| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
already part of things we'll change even if public (because, not part of lombok.X or lombok.experimental.X or lombok.experimental.**), nor is it particularly volatile.
See issue #389.
|
|
needing root access to install/uninstall lombok.
|
|
Lahoda of team Netbeans.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to need some special treatment to avoid a bug when generating constructors,
see: http://code.google.com/p/projectlombok/issues/detail?id=155
Since Eclipse 3.6 we are no longer able to reproduce this issue. The fix,
however, introduced bug 377 i.e. it was no longer possible to set break-points
on lines above generated methods/constructors.
tl;dr: Fixes #377, but does not reintroduce #155
|
|
maven-central for the 1.8.0 version
|
|
|
|
existing methods.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
though.
|
|
this has been fixed
|
|
|
|
- Moved Completion proposal code to the PatchExtensionMethodCompletionProposal
class
- Moved out error reporting from EclipseAST.
- Fixed error reporting of the portals.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the portal itself has lost it's function (Eclipse help is
currently failing, but this also seems to be caused by val).
Major point though is that the Extention methods functionality
works both in javac as in Eclipse.
|
|
the EclipseUtils.
|
|
|
|
Casual tests show that it is working. Taken from lombok-pg.
|
|
|
|
|
|
|
|
|
|
|
|
Also belatedly bumped version to 0.11.1.
|
