| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
- fix jboss-logging.jar name
- add copyright notice to new source files
- add cross-references from other @Log annotations
- update feature page
|
|
|
|
|
|
also handles the changed flag correctly
|
|
|
|
|
|
that we ignored earlier.
|
|
* Added ‘format’ directive for tests.
* Updates tests to salt in some more format and config keys.
|
|
|
|
|
|
|
|
|
|
|
|
and backslash U escapes.
|
|
|
|
IErrorHandlingPolicy in a more recent ecj editions
|
|
|
|
'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.
|
|
tests pass (new versions of javac, ecj, etc sometimes totally change the message).
|
|
they should now be able to handle running JDK8 etc tests.
CAREFUL: You MUST name your JDK8 'JavaSE-1.8' or it won't work.
Also added a basic test for JDK8 features.
|
|
against ecj8 to the lineup, and to force compilation with the bootstrap classpath of JDK6 so that we won't accidentally add deps on things that JVM6es don't have.
|
|
|
|
* 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').
|
|
For now, it fails.
|
|
content' signal; now you need an explicit directive to allow this behaviour.
[configuration] added tests for @Accessors configuration key implementations.
|
|
cases, and added first tests to test implementations of configuration-based stuff (FlagUsages, specifically). Error reporter has been refactored.
|
|
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.
|
|
which have become more important as input files now may need to set up some lombok configuration stuff.
|
|
|
|
@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.
|
|
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!
|
|
obviously doesn't work on windows; we force unix line ending now.
|
|
|
|
to be organization-name.jar instead of just name.jar, in order to account for
the ever lovely and wonderful apache's crazy decision to call the entirely
separate log4j v2.0 also 'log4j'. This does mean you'll have to 'ant clean'.
|
|
* 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.
|
|
|
|
eclipse for fields with @Deprecated on them.
|
|
more text (such as the explanation for why it is being ignored).
|
|
produced errors and warnings (i.e. we intentionally compile code with errors in them to verify that the appropriate error or warning message is emitted when lombok is active during a compilation run of either javac or ecj) - instead of string comparisons, it's a little more complex. This to enable testing of both javac6 and javac7, even if they produce (slightly) different error output.
Updated all message files in the 'expected output' directories to represent this change.
|
|
in our tests, the tests are in the unfortunate scenario where we always compile against a given javac (lib/build/javac6.jar), and always run the tests against a given javac, but that javac tries to use the bootclasspath of the host JRE, and if that is JRE7, you get all sorts of errors.
I fixed it by still compiling against a given javac (we can only ship one lombok.jar after all), but having the test task run with a given bootclasspath and a given javac.jar.
There are 2 tasks that download both rt.jar and javac.jar for either OpenJDK6 or OpenJDK7, and it writes a properties file with those locations. The test task will use this property file, and explain what you need to do if it is not there.
Incidentally, this brought to light issue 422: Delombok in java7 produces VerifyErrors.
|
|
on things to a directory (use -Dlombok.tests.dump_actual_files=/path/to/dir).
Useful if you KNOW lombok is working but something changed in output, i.e. order of generated methods.
|
|
|
|
|
