Age | Commit message (Collapse) | Author |
|
|
|
|
|
can't be @EqualsAndHashCode marked.
|
|
is) separately compilable, i.e. has no deps on any of the others.
This is preparation work for being able to access some of these from lombok.ast without creating a cyclic dependency nightmare.
|
|
In eclipse assigned final fields broke the @AllArgsConstructor. Now they are just skipped as intended.
|
|
|
|
also contains @SneakyThrows
|
|
|
|
|
|
was done for _every_ local declaration _anywhere_ in _any_ eclipse source file to see if it needed 'val' treatment. Now as a shortcut there's a check if the typeRef's last part is equal to 'val', and if not, no check is performed.
|
|
incapabilities. Issue #251
|
|
|
|
|
|
To support the new numeric literal syntax of Java 7, the constructor of IntLiteral got replaced by a factory-method. So we updated the affected handlers to work in both worlds.
|
|
skipPrintAst was a singleton global, so, yes, thread race issues all over the place.
|
|
|
|
this out in 0.10.0-RC2.
|
|
|
|
240.
|
|
|
|
|
|
|
|
even if its a post-diet handler.
|
|
interfaces; there were too many 'option' methods (methods where you return either true or false), so we really needed the ability to pick a default.
|
|
164' escape to not do that in ecj was no longer relevant.
|
|
because the 'isFullParse' boolean was erronously set on a full rebuild, forced by HandleDelegate.
HandleDelegate has also been updated to not do so much work if there's no @Delegate in a source file.
|
|
Synchronized and SneakyThrows
|
|
|
|
a severe error in PatchDelegate(issue #211) where classes that didn't use lombok at all could not be build due to a NullPointerException.
|
|
handled is only done if we are -actually- going to call a handler.
|
|
via the LombokAST object. Instead its tracked more directly in an attempt
to avoid having to write all handlers as idempotent, and just in case
issue #164 is a race condition (the handled-or-not is a synchronized CAS check).
This does break API for other plugins, but the fix is trivial: Just make your
'handle' method return void. That 'we won't call you again' business in the decks
never quite worked right anyway.
Also, you might want to call Javac.(recursive)setHandledBy when you generate nodes, now.
|
|
it won't actually work right; method-level generics would break.
The new way is to use -javaagent:lombok.jar=ECJ in addition to -cp lombok.jar
|
|
against situations in which lombok can't possibly work, since there is not enough of eclipse on the classpath. Major example of this is when we are called through jsps in the eclipse help.
Also added an extra check before the patchval is performed by checking if previous patch calls failed in TransformEclipseAST.
This fixes Issue #207.
|
|
|
|
NoSuchMethodError: CastExpression.<init>
This commit fixes this (now lombok works both <3.7 and 3.7).
fixes issue #206
|
|
a user runs into issue #164, we can get a more useful stracktrace from them.
|
|
|
|
Lombok.preventNullAnalysis but go with Collections.singletonList(expr).get(0)
instead; while this does create a pointless object, it doesn't cause a clash
when eclipse has lombok 0.10 installed but the project uses 0.9, which doesn't
have preventNullAnalysis. Eventually, once 0.9 is long forgotten, this can be reverted.
|
|
|
|
'isFoo', 'hasFoo', or 'getFoo' would trigger specialized handling for @Getter/@Setter. However, this special handling broke the bean spec, and has been simplified: Only fields named 'isFoo', and only if that field's type is 'boolean', results in both 'isFoo' and 'foo' being considered as possible property names for this property, with 'foo' preferred, so that @Getter boolean isFoo will generate setFoo and isFoo methods, not setIsFoo and isIsFoo.
Fixes issue #148
|
|
printed by EclipseASTVisitor.Printer
|
|
would cause 1 error log entry to show up. No other effects other than that, but thats ugly and so thats been fixed.
|
|
EclipseAST object.
Fixes issue #171
|
|
will still attempt to call this nonexistent getAbc instead of getABC. Fixed.
Fixes issue #173.
|
|
Object as parameter (creating new equals methods by giving them non-object parameterized is a _really_ bad idea, but if someone did do that, obviously lombok shouldn't call those!)
Fixes #165.
|
|
enums. Docs have been updated.
Behaviour of @XArgsConstructor when its placement makes no sense (i.e. when annotating an interface with them) is no longer 'throw weird errors', but has been brought in line with the others: A nice error message is generated.
Fixes issue #175
|
|
lombok.val without breaking 'fix imports'. Eesh. Using "lombok.val" only half-works; auto-complete on the variable doesn't work, but it compiles fine and no errors are reported.
|
|
methods.
|
|
- Removed the option to specify a different class to log on
- Updated tests and documentation
|
|
initialized.
|