| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Conflicts:
src/core/lombok/eclipse/handlers/EclipseHandlerUtil.java
|
|
or the parameter of the generated getter/setter methods.
|
|
fileds. Fixed. Thanks to Philipp Eichhorn for spotting this problem!
|
|
|
|
warnings about variables that cannot be null
|
|
package. fixed.
|
|
dependency for delombok users.
|
|
|
|
|
|
|
|
|
|
anything. Fixed.
|
|
and arrays no longer cause "Symbol not found: Array" errors.
|
|
|
|
|
|
|
|
http://code.google.com/p/projectlombok/issues/detail?id=155
Now all lombok generated methods are located before any other method.
|
|
|
|
their String representations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
systems with a javac that _does not_ close the annotation processor's jar. Fixed that, too.
|
|
javac, though for javac v1.6 you get false errors during compilation printed to stderr :(
|
|
more lombok classes to do its job, after javac has already closed the classloader via a hack. We hack the hack to stop javac from closing only _our_ (that is, lombok.jar's) classloader.
Co-Author: Roel
|
|
an ATHROW opcode.
|
|
|
|
|
|
|
|
|
|
|
|
type parameters. This resulted in delombok turning any generated constructor that takes at least 1 parameter of type 'T' into something that didn't compile, and to boot, a confusing error message. This is now fixed.
Fixes issue #140.
|
|
|
|
classes, fields and methods
|
|
|
|
|
