Installer adds relative path to lombok.jar to eclipse.ini under Windows 10

[Oliver Ferschke]

Hi,

first of all, I just started using Lombok and I love it. 

I just lombok'ed a larger project of mine.

I have been using Lombok with Eclipse Mars.1 under Ubuntu without trouble - installer auto-detected eclipse.

Under MacOS El Capitan, I had to manually specify the location of eclipse, but then it worked perfectly.

Under Windows 10, I also had to specify the eclipse location, but after doing the installation, eclipse didn't start any more.

Looking at eclipse.ini, the installer added

-javaagent:lombok.jar

The installers on other OSes specified the absolute path of lombok.jar

Changing the entry under Windows 10 to the absolute path of the jar solved this issues and everything worked as expected.

Not sure why this happened, but maybe this might be helpful for future reference.

Best,

Oliver

[Roel Spilker]

I have no problems on Windows 10 myself. 

Are you using a shortcut with a different starting directory to launch Eclipse?

We prefer relative paths to allow the user to rename or move the directory without breaking the Eclipse setup.

[Oliver Ferschke]

I used the "Eclipse Mars.1" 64bit installer for Windows 10 from eclipse.org, installed eclipse in the default folder and use the auto-created start menu entry to launch eclipse.

I just checked and I am able to launch eclipse with the relative path in the eclipse.ini when launching the binary directly from within the eclipse folder.

So it must be the start menu entry created by the eclipse Windows installer that messes things up on my machine.

I mainly use Ubuntu and MacOS where I don't use an installer to install eclipse, so I didn't think about this.