Age | Commit message (Collapse) | Author |
|
|
|
enforce only sensible exceptions and partly to make it possible to have the message be ‘x is null’ when throwing IAEs.
|
|
IllegalArgumentException vs. NullPointerException that we really don’t want to get into.
|
|
|
|
|
|
'optional' expected messages added.
expanded some tests.
Added a check if the bootclasspath supports a certain version, i.e. don't try to run a JDK7-only test if AutoClosable isn't available.
|
|
|
|
modified all onX examples to use two underscores.
|
|
Also fixed the total lack of canEqual in the usage examples.
|
|
* Conflict due to adding topic() feature to logger in master, and 'field name' feature in config branch.
* master has since updated to shiny new eclipse dep versions and the 'ant eclipseForDebugging' feature, but this branch added deps. Addressed that.
* Renamed 'loggerCategory' to 'loggerTopic'. I know, that wasn't exactly right to do in a merge, but, there you have it.
* Test infrastructure changed in configuration branch, and tests had been added in master branch.
Conflicts:
build.xml
buildScripts/ivy.xml
src/core/lombok/eclipse/handlers/HandleLog.java
src/core/lombok/extern/apachecommons/CommonsLog.java
src/core/lombok/extern/java/Log.java
src/core/lombok/extern/log4j/Log4j.java
src/core/lombok/extern/log4j/Log4j2.java
src/core/lombok/javac/handlers/HandleLog.java
test/transform/resource/after-ecj/ValInTryWithResources.java
|
|
features on ecj.
[Log] updated naming for @Log (topic= instead of mchmulder's 'value').
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and lombok.ToString.includeFieldNames
|
|
content' signal; now you need an explicit directive to allow this behaviour.
[configuration] added tests for @Accessors configuration key implementations.
|
|
|
|
|
|
now can start with directives (configuration keys, 'ignore', and java language version limits), and the test directory runner now has a framework to handle these. All existing tests pass at this point.
|
|
|
|
31, probably owing to its inclusion in Effective Java, is overused, as proven by Maaartinus in issue 625. Switching to 277 instead. Also, 1231/1237 pair used for booleans has been replaced by 2591/2609.
|
|
|
|
@Synchronized [Issue #588]
|
|
- 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.
|
|
@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.
|
|
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.
|
|
|
|
|
|
Added toString() impl for builders in both eclipse and javac.
Added all documentation, though it'll need some reviewing.
|
|
Eclipse's implementation continues to pass them all.
|
|
including docs and changelog.
|
|
generates a warning to explain this strange situation.
|
|
|
|
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.
|
|
|
|
in a ternary expression).
|
|
|
|
|
|
|
|
Conflicts:
src/core/lombok/javac/handlers/JavacHandlerUtil.java
|
|
parameters did not work in javac.
|
|
@XxxArgsConstructor is present means it gets ignored, but until now lombok didn't warn you about this.
|
|
|
|
|
|
|