Normally, lombok adds support for all the lombok features directly to your IDE and compiler by plugging into them.
However, lombok doesn't cover all tools. For example, lombok cannot plug into javadoc, nor can it plug into the Google Widget Toolkit, both of which run on java sources. Delombok still allows you to use lombok with these tools by preprocessing your java code into java code with all of lombok's transformations already applied.
Delombok can of course also help understand what's happening with your source by letting you look at exactly what lombok is doing 'under the hood'.
Delombok's standard mode of operation is that it copies an entire directory into another directory, recursively, skipping class files, and applying lombok transformations to any java source files it encounters.
Delombok is included in
lombok.jar. To use it, all you need to run on the command line is:
java -jar lombok.jar delombok src -d src-delomboked
srcdirectory into the
src-delombokeddirectory, which will be created if it doesn't already exist, but delomboked of course. Delombok on the command line has a few more options; use the
--helpparameter to see more options.
To let delombok print the transformation result of a single java file directly to standard output, you can use:
java -jar lombok.jar delombok -p MyJavaFile.java
lombok.jarincludes an ant task which can apply delombok for you. For example, to create javadoc for your project, your
build.xmlfile would look something like:
<target name="javadoc"> <taskdef classname="lombok.delombok.ant.DelombokTask" classpath="lib/lombok.jar" name="delombok" /> <mkdir dir="build/src-delomboked" /> <delombok verbose="true" encoding="UTF-8" to="build/src-delomboked" from="src" /> <mkdir dir="build/api" /> <javadoc sourcepath="build/src-delomboked" defaultexcludes="yes" destdir="build/api" /> </target>
fromattribute, you can also nest
public /*comment*/ static ...will move towards the front of the list of modifiers. In practice, any java source parsing tool will not be affected.