Starting eclipse with -vm parameter will stop lombok from loading.

[GoogleCodeExporter]

The -vm parameter wins out over VM parameters listed in eclipse.ini, and both -
Xbootclasspath/a and -javaagent are VM parameters.

Possible solutions:
 - Just warn people about that setup. Presumably they manually created the shortcut to do it, so 
they know what we would be talking about.
 - Auto-detect such shortcuts, but that seems infeasible. As a pure heuristic feature, we could 
warn if we luck out and do find one by e.g. scanning the Desktop and the 
quicklinks in windows, 
or any scripts that involve 'eclipse' in a user's bin directory on linux.
 - Start a FAQ and list this issue there.

Discussion:
 http://groups.google.com/group/project-lombok/browse_thread/thread/3293b490d238b3e3

Original issue reported on code.google.com by reini...@gmail.com on 5 Aug 2009 at 2:17

[GoogleCodeExporter]

For what it's worth (now almost a year after the issue was opened ;-)), I don't 
have a problem here. I can get Lombok to work via a command line shortcut with 
the following target:

"C:\Program Files\Eclipse\eclipse-java-helios-RC1-win32-x86_64\eclipse.exe"

with the following eclipse.ini:

-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.0.v20100503
-vm
C:/Program Files/Java/jdk1.6.0_20/bin/javaw.exe
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-server
-Xss1m
-XX:PermSize=64m
-XX:+DoEscapeAnalysis
-XX:+UseConcMarkSweepGC
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx768m
-Xbootclasspath/a:lombok.jar
-javaagent:lombok.jar

Environment: 

OS
--
Microsoft® Windows VistaT Business
6.0.6002 Service Pack 2 Build 6002

Eclipse (Helios)
-------
Version: 1.3.0.20100617-0520
Build id: 20100618-0524

Original comment by sharedo...@gmail.com on 14 Jul 2010 at 9:38

[GoogleCodeExporter]

the problem only occurs if you specify additional command line options. For 
instance, make your target the following:
"C:\Program Files\Eclipse\eclipse-java-helios-RC1-win32-x86_64\eclipse.exe 
-data d:\workspaces\foo"

Original comment by r.spilker on 14 Jul 2010 at 1:28

[GoogleCodeExporter]

I'm going to close this, because the installer now does warn about this 
situation, detecting it isn't feasible, and installing lombok into eclipse by 
directly messing with the module jars seems to be more hassle than its worth. A 
possible future eclipse plugin can take over the duty of detecting a problem 
(and/or injecting it during system load, now that java 1.6 is becoming more and 
more widespread).

Original comment by reini...@gmail.com on 14 Jul 2010 at 1:54

• Changed state: Verified