Accepted answer

did you add


to your eclipse.ini?

because if you have (and if you have added the lombok.jar to the libraries used by your project), it works just fine with eclipse helios:

alt text

ian tegebo mentions in the comments that:

a simple "restart" was not sufficient to pick up the changed vmargs:
i needed to explicitly exit and then start again.

chrisjleu mentions in the comments:

if you happen to be running a customized eclipse helios (3.6+) distribution then you may have to use the full path to lombok.jar in both the vm arguments.
see commit b47e87f for more details.

boolean fullpathrequired = idefinder.getos() == eclipsefinder.os.unix || system.getproperty("lombok.installer.fullpath") != null;


just faced this issue (compiler errors for generated getters) and none of the proposed solutions helped.

setup: eclipse oxygen (32bit), sap_jvm (32bit), lombok 1.16.18 (eclipse plugin properly installed).

created a plain new test project, which worked like a charm. afterwards deleted the failing project and checked it out again from my github repo, which fixed the errors. just deleting the project from the workspace and importing it again, didn't help.


i am using windows 10. i followed below steps :

  • added lombok dependency in pom.xml of my project
  • added "-javaagent:{pathoflombokjarinsystem}" in eclipse.ini file. path in my case was "-javaagent:c:\users\ {username} .m2\repository\org\projectlombok\lombok\1.18.6\lombok-1.18.6.jar"
  • started the eclipse and did maven > update project.

this resolved the issue for me.


i am using eclipse jee 2019-06 and this worked for me:

  • download lombok.jar
  • open cmd and run: java -jar lombok.jar
  • lombok config window will open.
  • in “specify location” set the path of the eclipse.exe (for example c:\users\<username>\eclipse\jee-2019-062\eclipse\eclipse.exe )
  • click “install/update”
  • quit installer
  • exit eclipse and open it again



for me, the cause is different. my project name in settings.gradle was different from project name in eclipse.

so make sure your eclipse project name is as same as in settings.gradle


i searched for lomob.jar in .m2 repo. once you double click it -> search eclipse.exe and select it. after lombok will make the required changes. explicitly quit eclipse -> it should be fixed by now. if not do a maven update.


i am on eclipse neon, and after following the above steps, it still didnt work. import; was not being recognized.

after about an hour of looking around, i switched the version to 1.16.14 and it worked.

now my thought is, whether the 1 hour spent will be a good investment for long term :-)


eclipse oxygen - after installation of lombok according to the process described on the lombok page, still could not use @log annotation.

solution : project --> properties - enable annotation processing


it was little frustrating. but finally it got resolved for me with following solution.

the issue seems to be where "-javaagent:lombok.jar" is placed in your ini file. when i installed it through lombok installation. this line got added towards last parameters after -vmargs. when i moved it up next to -vmargs. the issue got resolved.


if you are using windows xp and eclipse juno then it should be like this in order



i could not install lombok.jar on my macbook pro because of the version of java. i had to downgrade to java 1.6 to install and then i reused java 1.7 when the installation worked !

you can see the different jvm installed on your machine here : /system/library/java/javavirtualmachines


i had similar issue on macbook pro, i just followed the below link and issue got resolved.

steps followed:-

  • download the lombok.jar
  • double click on this jar
  • this jar will try to find the eclipse installed on the machine, but in my case it was not able to identify the eclipse though i installed on it, this could be due to softlink to the eclipse path.
  • i just specified the location of the eclipse ini file by clicking "specify location" button
  • this jar automatically updated the entry in eclipse.ini file for javaagent
    • i added the same jar to the classpath of the project in the eclipse
    • restarted my eclipse


remenber run lombok.jar as a java app, if your using windows7 open a console(cmd.exe) as adminstrator, and run c:"your java instalation"\ java -jar "lombok directory"\lombok.jar and then lombok ask for yours ides ubication.


this sometimes does not work if eclipse is on one of those strange default windows paths (e.g. c:/program files (86)/eclipse).

in that case, do as above, then move the lombok jar to a cleaner path without spaces and braces (e.g. c:\lombok\lombok.jar) and modify eclipse.ini accordingly.


i ran into this problem due to the missing:

-vmargs -javaagent:lombok.jar -xbootclasspath/a:lombok.jar

as well. what is not explicitly said neither here nor in the lombok popup message, and was not obvious to me as someone who never before had to fiddle with the eclipse.ini, is that you are not supposed to add that line, but instead add the last two parts of that line after the first part, which is already in the eclipse.ini file. to better illustrate, the end of the file should look something like this (bold is what matters for lombok, the rest might be different for you):

c:/program files/java/jdk1.7.0_02/bin


  1. copy the lombok jar into your eclipse based ide (eclipse/sts etc-) install folder

    • note that the install folder is the folder that has the .ini file for your ide
    • if you use maven to pull in the jar, then get it from your m2 repository
    • cp ~/.m2/repository/projectlombork/lombork-1.x.jar /path/to/ide/lombok.jar
  2. edit the .ini file in the install folder of your ide and add the following lines below -vmargs.

    • -javaagent:lombok.jar -xbootclasspath/a:lombok.jar
    • note that the jar should be in the same folder as the .ini file and the name of the jar lombok.jar
  3. restart your ide and rebuild/maven-update your project


this is for setup of lombok on spring tool suite. here is what i did on spring tool suite (sts-4.4.0.release) and lombok-1.18.10.jar (current latest version available in mavenrepository).

  1. if having maven project, ensure lombok dependency added to it. else you need manually add the jar to your project classpath.

    <!-- --> <dependency> <groupid>org.projectlombok</groupid> <artifactid>lombok</artifactid> <version>1.18.10</version> <scope>provided</scope> </dependency>

  2. clean build the maven application. this will download lombok jar in your .m2 location by default from maven repository. the path would be org\projectlombok\lombok\1.18.10\

  3. now open command prompt and navigate to the lombok path and execute command java -jar lombok-1.18.10.jar

    c:\xxx\xxx\org\projectlombok\lombok\1.18.10>java -jar lombok-1.18.10.jar

  4. opens up lombok dialog box. if see message can't find ide click specify location... provide the path to your sts root location

    my case it is c:\apps\sts-4.4.0.release\springtoolsuite.exe


  5. install successful click quit installer

  6. now in explorer navigate to your sts root path. c:\apps\sts-4.4.0.release\ we see lombok.jar placed in the sts root path now edit in notepad springtoolsuite4.ini file we see following appended at the end


  7. start sts using springtoolsuite4.exe clean, rebuild your project.


i can only make this work if i start the eclipse.exe directly in the eclipse installation folder. if i use a command file setting some initial java_home and maven parameters before running the eclipse.exe it does not work and i get compiler errors on the exact same projects


don't forget to do to project->clean in eclipse to make sure that your classes are recompiled.


please follow the following steps:- if lombok jar has already been added as dependency in eclipse, then go to project's lib folder > locate lombok.xx.jar > right click on jar> run as java application> this will launch lombok screen as below:- enter image description here

next, click on "specify location" > and specify location of "eclipse.ini" file.(eclipse neon on mac osx has it at -> "<eclipse_installation_path>/jee-neon/").

after this, restart eclipse and clean build project.

this worked for me.


after adding lombok and restarting eclipse or spring tools my project still failed to recognize getters and setters. red markers everywhere!

the solution: right-click your project, go to maven and select update project

after hours of searching and trying random solution, i find this to be the only solution that worked for me.

enter image description here


you not only have to add lombok.jar to the libraries, but also install it by either double-clicking the lombok jar, or from the command line run java -jar lombok.jar. that will show you a nice installer screen. select your eclipse installation and install.

afterwards, you can check if the installer has correctly modified your eclipse.ini:


if your eclipse was already running, you have to exit eclipse and start it again. (file/restart is not enough)

if you are starting eclipse using a shortcut, make sure that either there are no command line arguments filled in, or manually add -javaagent:lombok.jar -xbootclasspath/a:lombok.jar somewhere after -vmargs.

recent editions of lombok also add a line to the about eclipse screen. if lombok is active you can find a line like 'lombok v0.11.6 "dashing kakapo" is installed.' just above the line of buttons.

if for some reason, usually related to customized eclipse builds, you need to use the full path, you can instruct the installer on the command line to do so:

java -dlombok.installer.fullpath -jar lombok.jar

Related Query

More Query from same tag