| Age | Commit message (Collapse) | Author |
|---|
|
|
|
@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.
|
|
has moved from experimental into core).
|
|
Eclipse breaks the javadoc out of the raw source and we can't modify that without breaking a billion things. To solve this issue we'd have to write some very complicated patches to intercept this process and somehow propagate the node that the javadoc is attached to AND translate from the ast model to dom or whatever is being used there. Not gonna happen for this low priority feature.
|
|
javadoc for getters/setters, and fixed pretty printer to no longer inject an extra newline at the top of javadoc.
|
|
as updates to all relevant documentation
|
|
javadoc from field to setter/getter in javac.
|
|
|
|
|
|
Implementing in javac, ecj still has to be done.
|
|
This caused a bunch of weirdness because eclipse changes a bunch of warnings and quickfixes based on this (such as complaining about lack of @SafeVarargs, a 1.7-only feature).
|
|
where _ANY_ mention of com.sun.tools.javac.tree.TreeMaker,
anywhere in a source file, would disable pretty much every
intelligent part of what makes the 'I' in IDE in eclipse:
No auto-complete, no 'go to declaration', etcetera, but only
since Eclipse Juno (not fixed in Kepler either). It's the
presence of src/stubs/com/sun/tools/javac/util/Context.java.
I've moved Context to a special stubs directory that's only used
for javac (so that we still get the benefit of getting some
warnings and such when making command line builds), and removed
the @Override annotations for where the stubbing is relevant
(for methods that exist in javac7 but not in javac6 on interfaces
we create implementations of). Furthermore, I did some extremely
tricky work in making our version actuall compatible with the
exact class signatures of both javac6- and javac7+'s versions;
generation of synthetic methods for reified type parameters was
causing havoc.
A big stack of 'here be voodoo' comments unfortunately added to
explain it all; necessary evil.
|
|
|
|
proper paths on Windows
|
|
where we still support it as an alias. fixed.
|
|
|
|
experimental one is now deprecated.
|
|
|
|
Added toString() impl for builders in both eclipse and javac.
Added all documentation, though it'll need some reviewing.
|
|
javac1.7. (The wrapper uses reflection). Need for: javac @Builder impl.
Also added some utilities to JavacHandlerUtil.
|
|
some minor updates and refactoring in the eclipse HandleBuilder.
|
|
|
|
|
|
inject the created $Builder type.
Inspired by Philipp Eichhorn's work in lombok-pg.
|
|
reason... now I'm just confused. Do we need it or not?
|
|
|
|
parse tree builder under javac. Let's hope our users reporting these
issues can use this to figure out which files are triggering the issue.
|
|
including docs and changelog.
|
|
|
|
|
|
and updated ECJ version detection.
|
|
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)
|
|
platform and implemented it for javac BUT NOT FOR ECJ!
|
|
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.
|
|
would fail with VerifyError when that code is executed in eclipse.
|
|
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.
|
|
|
|
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.
|
