[IMPROVEMENT]

Eclipse will now also hold off on running @PrintAST handlers until the very end. Simple generators such as @Getter didn't need this, because PrintAST's handler will hold off until eclipse does a full parse,
but when changing the innards of methods, you would likely not see what you did. Fixed that.

Also, PrintAST has an option to, instead of diving into the ASTNodes of bodies (methods, initializers, etc), to just render the java code, to see if the AST creation/rewriting you've been doing looks like the java code you intended.

1 files changed, 6 insertions, 0 deletions

diff --git a/src/lombok/core/PrintAST.java b/src/lombok/core/PrintAST.java
index 9fb12b2c..6d1eaafd 100644
--- a/src/lombok/core/PrintAST.java
+++ b/src/lombok/core/PrintAST.java
@@ -9,4 +9,10 @@ import java.lang.annotation.Target;
 @Retention(RetentionPolicy.SOURCE)
 public @interface PrintAST {
 	String outfile() default "";
+	
+	/**
+	 * Normally, the printer will print each node focusing on the node (E.g. classname, and such). By setting printContent to true,
+	 * methods, initializers, and other statement-containing elements actually print their java code instead of element class names.
+	 */
+	boolean printContent() default false;
 }