If val errors out, now at least you see where it happened.
Updated copyright header in website feature pages.
Patches ASTNode.setSourceRange; by default it throws IllegalArgumentExceptions in certain cases, but with no message, thus making it very hard to figure out what went wrong. The patch throws the same exceptions in the same cases, but gives the exception a useful error message.
Ever since we do a lot more than just calling 'parse' when running delombok 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.
Fixes issue 422: VerifyError when running delombok in a javac7 environment.
Typo fixes in build.xml
Fix for NPEs in the eclipse log for
org.eclipse.jdt.internal.compiler.lookup.MethodBinding.sourceMethod(MethodBinding.java:1108)
added previous fix to changelog.
Updated the setup test environment tasks in the build script to produce eclipse launch targets IF the project has been treated as eclipse project ('.project' is present).
The testrunner now uses a different mechanism to verify correctness of 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.
Empty statements no longer being printed to be consistent with Javac7 which seems to just remove these from the AST entirely.
fix for issue #423: @ExtensionMethods failed with an NPE in the handler on javac if generated constructors are involved.
//ignore in files now counts even if the 'ignore' comment is followed by more text (such as the explanation for why it is being ignored).
added tests for lub and val (lub = finding the common supertype, for example in a ternary expression).
Fix for issue 408: IllegalArgumentException when generating setters in eclipse for fields with @Deprecated on them.
Added annotation for the slf4j extended logger
pre-release version bump
post-release version bump.
whoops forgot to update changelog for release 0.11.6
[refactor] Cleaned up static imports (always use *), and refactored out getCtcInt calls into constants as defined in Javac.