Age | Commit message (Collapse) | Author |
|
in our tests, the tests are in the unfortunate scenario where we always compile against a given javac (lib/build/javac6.jar), and always run the tests against a given javac, but that javac tries to use the bootclasspath of the host JRE, and if that is JRE7, you get all sorts of errors.
I fixed it by still compiling against a given javac (we can only ship one lombok.jar after all), but having the test task run with a given bootclasspath and a given javac.jar.
There are 2 tasks that download both rt.jar and javac.jar for either OpenJDK6 or OpenJDK7, and it writes a properties file with those locations. The test task will use this property file, and explain what you need to do if it is not there.
Incidentally, this brought to light issue 422: Delombok in java7 produces VerifyErrors.
|
|
|
|
meant the top-level debug dir, not any file named debug.
|
|
launch config that adds the appropriate -javaagent VM param to ensure the runWithEclipse tests work.
|
|
so we no longer need our own repository. Also updated publish process to new server (escudo is in, libertad is out).
|
|
.markdown files.
|
|
patch on, to do so. This involved switching to ivyplusplus 1.4 and includes a hack to make sure 1.3 users get upgraded.
|
|
|
|
|
|
fetch and unpack findbugs from its sourceforge repository. Still need to figure out how to maintain a list of findbugs warnings that findbugs should be ignoring.
|
|
|
|
now done automatically by this script, which also means that e.g. lombok-patcher.jar no longer needs to be checked in.
|
|
nicer. The old runEclipse scripts are now useless, so they have been removed.
|
|
|
|
|