Age | Commit message (Collapse) | Author |
|
|
|
Also fixed a bug where eclipses installed in user.home weren't found automatically on windows.
Also fixed a bug where STS installed in C:\Program Files (X86) wasn't found automatically.
|
|
|
|
to be organization-name.jar instead of just name.jar, in order to account for
the ever lovely and wonderful apache's crazy decision to call the entirely
separate log4j v2.0 also 'log4j'. This does mean you'll have to 'ant clean'.
|
|
|
|
After this was finalized I realize that we might consider moving entirely
to String based options, instead of inferring the options from the
provided enum. This setup does have the benefit of throwing exceptions when
options are not present.
|
|
that JDK8 behaves similar to JDK7.
|
|
Only Oracle provides builds for JDK8 atm, and there is no OpenJDK
build, so the setup is slightly different. Files have to be copied
manually from an installed JDK. For comparison purposes, an Oracle JDK7
option has been added too. This should be removed before merging to master.
|
|
|
|
a few or no withers at all, and adding them is a lot simpler than
removing them. This is a breaking change, but then that's why @Value
was in experimental in the first place.
|
|
|
|
|
|
* re-introduction of onMethod/onConstructor/onParam
* tests checking error/warnings rewritten to be more heuristic, in order to accomodate difference in messaging between java6 and java 7
* Ability to eliminate java's own output of erroneous error messages (heh); i.e. those messages that are invalidated by lombok's actions. This mechanism is used for onMethod/onConstructor/onParam
* First steps to unifying a billion setGeneratedBy calls into a single visitor traversal for eclipse' HandleGetter/Setter/Constructor/Wither
* To simplify 'zooming in' the tests on just a few files, added an 'accept' mechanism.
* Updated copyright headers of website to 2013.
|
|
Now to actually write the feature (Well, rescue it from the onX-removal tag).
|
|
* Removed most documentation and instead put in a link to the much more up to date and extensive documentation at http://projectlombok.org/features
* Getting ahead of ourselves a little, added notes on onConstructor/onParam/onMethod which we are about to add in the next few commits.
* Updated copyrights to 2012.
|
|
(With thanks to Bart Enkelaar)
|
|
getCtcInt calls into constants as defined in Javac.
|
|
|
|
|
|
|
|
|
|
eclipse for fields with @Deprecated on them.
|
|
in a ternary expression).
|
|
more text (such as the explanation for why it is being ignored).
|
|
javac if generated constructors are involved.
|
|
seems to just remove these from the AST entirely.
|
|
produced errors and warnings (i.e. we intentionally compile code with errors in them to verify that the appropriate error or warning message is emitted when lombok is active during a compilation run of either javac or ecj) - instead of string comparisons, it's a little more complex. This to enable testing of both javac6 and javac7, even if they produce (slightly) different error output.
Updated all message files in the 'expected output' directories to represent this change.
|
|
eclipse launch targets IF the project has been treated as eclipse project ('.project' is present).
|
|
|
|
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.sourceMethod(MethodBinding.java:1108)
|
|
|
|
|
|
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.
|
|
IllegalArgumentExceptions in certain cases, but with no message, thus making it very hard to figure out what went wrong. The patch throws the same exceptions in the same cases, but gives the exception a useful error message.
|
|
|
|
|
|
See issue 411.
|
|
both eclipse/ecj and javac operations.
|
|
|
|
setting the annotation you handle for an XAnnotationHandler<T>;
default behaviour still extracts the T part out of the signature.
|
|
|
|
|
|
in eclipse for @ExtensionMethod, resulting in VerifyErrors in the emitted class files.
|
|
|
|
This also meant delombok would not emit the changed code if that's all that changed, because it thought nothing changed.
|
|
|
|
|
|
|
|
the handlers in the next priority level need it.
|
|
|