| Age | Commit message (Collapse) | Author |
|---|
|
@Synchronized [Issue #588]
|
|
Conflicts:
src/core/lombok/core/Version.java
src/core/lombok/javac/handlers/HandleConstructor.java
test/transform/resource/messages-delombok/EqualsAndHashCodeWithSomeExistingMethods.java.messages
test/transform/resource/messages-ecj/EqualsAndHashCodeWithSomeExistingMethods.java.messages
|
|
- Prevent NPE in javac and give a proper warning in both eclipse and javac
- Add test cases
|
|
@Accessors to handle field accessors.
* various operations on names in javac were really slow; they are faster now.
|
|
annotation for onX instead of single underscore, which emits warnings on javac8+.
Also made dollars and Xes legal in addition to underscores, in case double underscore disappears later too.
|
|
|
|
@Value's final-by-default and private-by-default with it; now
appropriate warnings are emitted)
* Builder now errors out on presence of most lombok annotations on an
explicit builder class.
* Builder now takes @FieldDefaults/@Value into account.
* Builder on type now generates the constructor as package private
instead of private to avoid synthetic accessor constructors.
* added a bunch of test cases.
* added a test case feature: If the expected file is omitted entirely
but there are expected messages, the differences in the output itself
are ignored.
* streamlined checking for boolean-ness (removed some duplicate code)
* added 'fluent' and 'chain' to @Builder.
|
|
coming up in autocomplete dialogs when guava's was intended.
|
|
|
|
|
|
Added toString() impl for builders in both eclipse and javac.
Added all documentation, though it'll need some reviewing.
|
|
some minor updates and refactoring in the eclipse HandleBuilder.
|
|
|
|
|
|
inject the created $Builder type.
Inspired by Philipp Eichhorn's work in lombok-pg.
|
|
including docs and changelog.
|
|
|
|
AST/LombokNode. Tests updates to honour these with //version X at the top
of any test file (now also in eclipse, which until now always said it was v6)
|
|
generates a warning to explain this strange situation.
|
|
other lombok plugin developers.
|
|
because it is a lot more work than anticipated, but this code is prettier and slightly more bugfree so worth checking in.
|
|
are abstract classes.
|
|
fixes the issue where delombok would leave lombok annotations in the file if that annotation had no actual effect (such as @Getter on a field if there is an explicit getX method for that field).
issue #443: delombok would screw up @SneakyThrows on methods or constructors with empty bodies. Now we generate warnings for this.
|
|
|
|
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.
|
|
getCtcInt calls into constants as defined in Javac.
|
|
|
|
eclipse for fields with @Deprecated on them.
|
|
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.
|
|
This also meant delombok would not emit the changed code if that's all that changed, because it thought nothing changed.
|
|
system for javac and ecj.
* @Value now makes the class itself final by default.
|
|
annotations including @NonFinal and @PackagePrivate, and some refactors. No tests yet.
|
|
|
|
Conflicts:
src/core/lombok/javac/handlers/JavacHandlerUtil.java
|
|
refactors to HandleSetter
|
|
0.11.2 due to a fix involving WeakHashMaps for lazy getters of type boolean.
|
|
@XxxArgsConstructor is present means it gets ignored, but until now lombok didn't warn you about this.
|
|
|
|
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.
|
|
|
|
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
|
|
|
|
|
|
|
|
- Moved Completion proposal code to the PatchExtensionMethodCompletionProposal
class
- Moved out error reporting from EclipseAST.
- Fixed error reporting of the portals.
|
|
|
|
|
