Added (and left intentionally undocumented) an option to force the installer to use an absolute path for location of lombok.jar:

java -Dlombok.installer.fullpath -jar lombok.jar

There have been some reports that under helios the relative path no longer cuts it, but all reports come from tweaked installs. In case folks run into this, we can now give them a quick solution.

See: http://groups.google.com/group/project-lombok/browse_thread/thread/2071edd5495a8cd7

1 files changed, 1 insertions, 1 deletions

diff --git a/src/installer/lombok/installer/eclipse/EclipseLocation.java b/src/installer/lombok/installer/eclipse/EclipseLocation.java
index 13142740..a17c9435 100644
--- a/src/installer/lombok/installer/eclipse/EclipseLocation.java
+++ b/src/installer/lombok/installer/eclipse/EclipseLocation.java
@@ -237,7 +237,7 @@ public class EclipseLocation extends IdeLocation {
 		// If someone knows how to fix this, please do so, as this current hack solution (putting the absolute path
 		// to the jar files in your eclipse.ini) means you can't move your eclipse around on linux without lombok
 		// breaking it. NB: rerunning lombok.jar installer and hitting 'update' will fix it if you do that.
-		boolean fullPathRequired = IdeFinder.getOS() == EclipseFinder.OS.UNIX;
+		boolean fullPathRequired = IdeFinder.getOS() == EclipseFinder.OS.UNIX || System.getProperty("lombok.installer.fullpath") != null;
 		
 		boolean installSucceeded = false;
 		StringBuilder newContents = new StringBuilder();