lombok 1.14.4 causes Eclipse to hang while loading EJB 3.1 deployment descriptors

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install lombok 1.12.2 as Eclipse agent (Kepler, including latest JBoss Tools 
plugin) and start Eclipse
2. create some Maven project using EJB 3.1 / JPA 2.0 and lombok 1.14.4 in 
pom.xml
3. create some stateless or session beans (e.g. DAOs) which use lombok 
annotations and use JPA entities which also make use of Lombok (@Getter, 
@Setter, @Slf4j, @EqualsHashCode, @ToString)
4. make sure the EJB 3.1 "Deployment Descriptor" of your EJB module is able to 
show e.g. the "Session Beans"
5. close Eclipse
6. Replace you Eclipse lombok agent jar with (today's latest) 1.14.4 version 
(version 1.14.4 can remain in you Maven project's pom.xml)
7. now start Eclipse again
8. if Eclipse is configured to automatically build your projects after Eclipse 
start, you will now see that Eclipse hangs with 100% single CPU utilization and 
is not able to show the EJB 3.1 "Deployment Descriptor" - even worse: this 
blocks every action you do in Eclipse, so it becomes totally unusable and you 
need to kill Eclipse java process finally to escape...

What is the expected output? 
The EJB 3.1 Deployment Descriptors in Eclipse can be loaded with lombok 1.14.4, 
as it does for 1.12.2.

What do you see instead?
The EJB 3.1 Deployment Descriptors in Eclipse cannot be loaded. Eclipse hangs 
as detailed above unter figure 8.

What version of the product are you using? On what operating system?
1.14.4 resp. 1.12.2 as fallback

Please provide any additional information below.
I can make my Eclipse environment and Maven project available for download, 
once you accepted the issue and it is really a new one or if you cannot 
reproduce it...

Original issue reported on code.google.com by u023...@googlemail.com on 21 Aug 2014 at 11:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OS: Windows 7
Eclipse Kepler SR2 build 20140224-0627
JDK 1.7.0_60

Original comment by u023...@googlemail.com on 21 Aug 2014 at 11:46

[GoogleCodeExporter]

What happens if you download the latest edge release and put this in your 
eclipse.ini, somewhere below -vmargs:

-Dlombok.disableConfig

Does that fix the problem?

http://projectlombok.org/download-edge.html

Original comment by r.spilker on 21 Aug 2014 at 8:28

[GoogleCodeExporter]

Original comment by r.spilker on 21 Aug 2014 at 8:28

• Changed state: Parked

[GoogleCodeExporter]

Hi! Thanks for your quick reply.

Well if I do what you suggested, it works fine again (but I only tested that 
the Deployment Descriptors are being loaded). After that successful test I shut 
down Eclipse and tried again with 1.14.4, but it still hangs then...

Here my working eclipse.ini with latest edge release + -Dlombok.disableConfig:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140116-2212
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512mM
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dsun.rmi.dgc.client.gcInterval=3600000
-javaagent:lombok-edge-1.14.5-20140821-2024.jar
-Xbootclasspath/a:lombok-edge-1.14.5-20140821-2024.jar
-Dosgi.requiredJavaVersion=1.6
-Dlombok.disableConfig
-Xms256m
-Xmx3072m

Here the one with 1.14.4, which fails:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140116-2212
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
512mM
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dsun.rmi.dgc.client.gcInterval=3600000
-javaagent:lombok-v1.14.4.jar
-Xbootclasspath/a:lombok-v1.14.4.jar
-Dosgi.requiredJavaVersion=1.6
-Xms256m
-Xmx3072m

Original comment by u023...@googlemail.com on 22 Aug 2014 at 8:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here my hanging Eclipse as screenshot... I marked the places where you can see 
that nothing happens - this was after hang of appx. 5mins.

Original comment by u023...@googlemail.com on 22 Aug 2014 at 9:02

Attachments:

• lombok-issue-730-eclipse-screenshot-20140822.PNG

[GoogleCodeExporter]

And this is a screenshot how it should be... Session Beans are being displayed 
properly in Eclipse's "Project Explorer".

Original comment by u023...@googlemail.com on 22 Aug 2014 at 9:06

Attachments:

• lombok-issue-730-eclipse-screenshot-working-20140822.PNG

[GoogleCodeExporter]

We're working on getting to the source of the problem. The 1.14.6 release 
supports the -Dlombok.disableConfig flag, so you should be able to use that 
version. Also, we did find some other opportunities to make things faster. Can 
you test that version and tell us your findings?

Original comment by r.spilker on 9 Sep 2014 at 6:42