aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorReinier Zwitserloot <reinier@zwitserloot.com>2010-07-17 06:58:00 +0200
committerReinier Zwitserloot <reinier@zwitserloot.com>2010-07-17 06:58:00 +0200
commit51b031c732a86cb28b35c9b6c9b31916d3846c88 (patch)
tree16d8ec236f4a62def50a867eeed365f959cdc48b
parent89586dd793c61f047afda3e34a92487815cc04e3 (diff)
downloadlombok-51b031c732a86cb28b35c9b6c9b31916d3846c88.tar.gz
lombok-51b031c732a86cb28b35c9b6c9b31916d3846c88.tar.bz2
lombok-51b031c732a86cb28b35c9b6c9b31916d3846c88.zip
In our efforts to eliminate annotations for delombok, we also eliminated all traces of the annotation for lombok itself. This didn't work well with @Data and how it interacts with existing @Getter/@Setter annotations. @Data scans for those annotations to determine that it shouldn't do anything. By deleting them, this process wasn't working anymore.
-rw-r--r--src/core/lombok/javac/handlers/JavacHandlerUtil.java1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/core/lombok/javac/handlers/JavacHandlerUtil.java b/src/core/lombok/javac/handlers/JavacHandlerUtil.java
index c968a9f7..499340bc 100644
--- a/src/core/lombok/javac/handlers/JavacHandlerUtil.java
+++ b/src/core/lombok/javac/handlers/JavacHandlerUtil.java
@@ -89,7 +89,6 @@ public class JavacHandlerUtil {
//This really shouldn't happen, but if it does, better just break delombok instead of breaking everything.
return;
}
- parentNode.removeChild(annotation);
JCCompilationUnit unit = (JCCompilationUnit) annotation.top().get();
deleteImportFromCompilationUnit(unit, annotationType.getName());