Migrated from Google Code (issue 363)
👤 email@example.com 🕗 Apr 17, 2012 at 04:20 UTC
What steps will reproduce the problem?
What is the expected output? What do you see instead?
No errors for lombok generated objects, instead, I noticed at least with @ Slf4j, the 'log' object was not recognized.
What version of the product are you using? On what operating system?
0.10.8 on Mac OS X
Please provide any additional information below.
👤 friesoft 🕗 Apr 20, 2012 at 07:29 UTC
Is there any eta for fixing this?
👤 r.spilker 🕗 Apr 20, 2012 at 07:47 UTC
Sorry, not yet.
👤 firstname.lastname@example.org 🕗 Apr 23, 2012 at 16:12 UTC
Hello, I found this appears to just be a problem with the lombok installer, not with lombok itself.
I found that if I manually add the following to eclipse.ini:
And copy the lombok.jar file into the same directory, it seems to work ok.
Its possible I did something wrong when I did the lombok installation. I am on a Mac, and Lombok did not find my ide, so I manually pointed it to the Eclipse Juno installation.
👤 friesoft 🕗 Apr 23, 2012 at 16:14 UTC
lombok itself works but slf4j does not - and maybe other things - that's what this report is about :)
👤 email@example.com 🕗 Apr 24, 2012 at 18:34 UTC
I know what the bug is about, I created it. Once I manually set the lines above in the eclipse.ini file, and I copied the lombok jar, I had no errors from missing lombok-generated fields in Eclipse Juno.
Specifically, Eclipse recognized a lombok-generated 'log' object, created with the @ Slf4j annotation.
I can't be 100% positive, but I suspect the only problem with Eclipse Juno is the installation process.
👤 r.spilker 🕗 Jul 02, 2012 at 22:22 UTC
We've just released 0.11.2 "Dashing Kakapo". Can you still reproduce the problems with that release?
👤 pardsbane 🕗 Jul 02, 2012 at 23:26 UTC
I don't know about 0.11.2, but I just installed 0.11.0 into the Juno release without problems.
👤 freeboy.jian 🕗 Jul 10, 2012 at 01:39 UTC
i installed release 0.11.2 with eclipse-jee-juno. works fine
👤 reinierz 🕗 Jul 10, 2012 at 23:32 UTC
Now try to uninstall it :)
0.11.4 will also fix this problem with the uninstaller. Already fixed in edge build.
👤 warchildwts 🕗 Aug 19, 2012 at 19:34 UTC
I just downloaded a fresh juno installation and tried 0.11.4 and have this bug still. I checked my eclipse.ini and it has lombok in it. The outline in eclipse sees the log object created by @ Log4j, code completion finds it, but I still get a java error that says log cannot be resolved. Even more interesting is if I right click on the error it gives me the option to change log to log.
👤 warchildwts 🕗 Aug 20, 2012 at 06:00 UTC
Ok, I just discovered the issue in my previous post. It appears that my project was having issues because it was also an aspectj project that also requires a java agent. If I disable aspectj, lombok works as expected.
👤 CMordant1 🕗 Oct 07, 2012 at 20:59 UTC
And what if I have an AJDT + Lombok project (Typically using @ Slf4j + @ Configurable annotation...)?
👤 michaelowl 🕗 Oct 13, 2012 at 20:52 UTC
I had the same problem with STS 3.1.0 and lombok 0.11.4 using the installer.
I fixed it by manually moving the lines added by the installer from the end of the sts.ini-file, right after the line with "-vmargs".
My -vmargs config in sts.ini now looks like this:
👤 julyguo7 🕗 Dec 03, 2012 at 04:58 UTC
Same problem here, java EE Juno with lombok 0.11.6, seem only the @ Log can not recognized in my environment. @ Getter @ Setter works fine.
👤 firstname.lastname@example.org 🕗 Jan 28, 2013 at 21:47 UTC
I too was having this issue on:
Mac OS X 10.8.3
Eclipse Juno SR1
The problem was only occurring on projects configured with AspectJ (AJDT). Once I remove the AspectJ nature from the Eclipse project, I was good to go.
👤 jmorkel 🕗 Sep 30, 2013 at 15:49 UTC
I'm also seeing this issue on AspectJ projects in Juno affecting the log object (added by @ Log4j) not being resolvable. Removing the AspectJ capability on the project fixes it, though now my use of AspectJ is hobbled in Eclipse.
The log object shows up in the class outline and the syntax highlighting indicates that the log object is a static field.
Any ideas on if a fix for this will be available any time soon?
👤 shawnhenryyao 🕗 Dec 13, 2013 at 08:16 UTC
awesome, solved my problem :) got exactly the same problem and its really stuck me a while, the first i did exactly the same steps that modified eclipse.ini and copy the lombox.jar to file into the same directory and then restarted eclipse but wasn't working, i got confused but when i deleted the log object and then rewrote it then it's working. anywhere thanks a lot.
End of migration