I have followed how to configure lombok in eclipse luna but it is not working for me for a given gradle project, against the latest version of lombok, having tried both eclipse Luna and Mars.
I have installed lombok to my eclipse through java -jar lombok.jar, providing it the path to my eclipse installation in the UI dialog that it opens up.
I have also added the jar to the project, as seen below.
I added the following argument to the java command in my desktop launch script (this is Ubuntu)
-vmargs -javaagent:lombok.jar
(relative and absolute paths worked the same).
The project is a gradle project, and it builds perfectly fine outside of eclipse.
What might be missing, or, how would I further troubleshoot it?
Related
I've encountered a very curious case about Eclipse and Spock tests.
I have Eclipse 4.5.2 (Build id: 20160218-0600) with Groovy compilers plugins installed, Groovy-Eclipse M2E Integration and Groovy-Eclipse Feature, all in version: 2.9.2.xx-201604081629-e45.
In this Eclipse I have a maven project configured to compile and run Spock tests. In Eclipse I have src/test/groovy folder configured as a source folder and it is holding my spock tests. Both maven and Eclipse can run the tests just fine.
Recently my friend has had a problem with the same setup, so I tried to reproduce it. And now I have the same Eclipse 4.5.2 (Build id: 20160218-0600) with Groovy plugin (and this is the weird part, I used the same update site for these plugins but the build version is different, it is: 2.9.2.xx-201607251752-e45). I imported the same maven project, however, when I try to run Spock tests the curious thing happens: the src/test/groovy source folder dissappears from the project and on the console I can see ClassNotFoundException with the name of the Spock test class. Here is a short summary how it looks like:
We tried the same also in Eclipse Neon and Spring STS and we have the same result. (In IntelliJ the same project runs just fine).
I'm starting ti thing that this may be related to the Groovy plugins, which might have got changed in the latest build and a bug was introduced. However, I hope I am mistaken.
Any thoughts?
I have eclipse version: "Mars Release (4.5.0)"
I have downloaded latest lombok jar from: https://projectlombok.org/download.html
I executed:
java -jar lombok.jar install $eclipseDir
After this I can see lombok.jar in my eclipse directory and eclipse.ini.
Restarted eclipse with:
eclipse -clean
But still lombok is not working for me.
I had the same problem. What helped was:
Restart Eclipse
Select from top menu Project -> Clean...
Clean all projects that use Lombok
If it will not help, try again from point 1. (I know it sounds stupid but it worked on my PC on second try.)
Also, I'm using Lombok version 1.16.4 (and Eclipse Mars of course)
BTW: Make sure that you have lombok.jar in the eclipse directory.
I have solved the same problem, here are my steps
check eclipse.ini, make sure lombok is properly installed
restart eclipse
project->clean, clean your project
window->show view->problems, Ctrl+A to select ALL errors, right
click & delete
project->clean, clean your project again
I think that should work.
I was facing the same issue in Eclipse Neon.2 and in STS 3.8.3 the solution was
Download the Lombok jar from
https://projectlombok.org/download.html
Execute
java -jar lombok.jar
Configure the Eclipse or STS and install.
It will copy the lombok.jar under Eclipse dir and add the line -javaagent:../Eclipse/lombok.jar in eclipse.ini or STS.ini
Make sure in About eclipse -> Installation Details -> Configuration
-javaagent:../Eclipse/lombok.jar line exists
If it's a git project then delete the project from workspace and import the project again. or else export the project and then import it again
Hope it helps someone!
On mac os this is because the location of eclipse.ini has changed. Kepler and Luna used Eclipse.app/Contents/MacOS/eclipse.ini. Mars uses Eclipse.app/Contents/Eclipse/eclipse.ini.
It looks like this has broken Lombok's Eclipse auto-detection as well.
eclipse.ini edit and project clean
-vmargs
-javaagent:lombok.jar
run the jar- I just double clicked on it;
Add the following to eclipse .ini, and have lombok.jar in the eclipse folder
-vmargs
-javaagent:lombok.jar
Windows 7 + eclipse mars
Have the same problem with Ubuntu 14.04, when I jump into eclipse directory and run the executable there, it is ok, however when the launcher icon is used, the entire eclipse.ini is being ignored for some reason.
Had similar problem with Neon. The problem was that the version of lombok.jar installed in the Eclipse directory was not the same as the version specified in pom.xml.
I'm struggling to get the Eclipse FindBugs plugin to work and am sure there's a schoolboy error being made somewhere.
I extracted the file findbugs-2.0.2-rc2.zip to a local folder C:\Program Files\findbugs-2.0.2-rc2 and running findbugs.bat, FindBugs works fine running it over a local Java (Eclipse) project.
I added the FindBugs update site, it found "FindBugs Feature, 2.0.1.20120712" and installed it. Restarting, right-clicking on an open Java Project doesn't display the "FindBugs" option (that this video shows).
I looked in Window > Preferences to try to find a way to inform the plugin of the local FindBugs installation (in Program Files), but couldn't find anything.
Uninstalling "FindBug Feature", I tried extracting the FindBugs Eclipse plugin zip file into Eclipse's plugins folder, but after a restart, saw no difference.
Help > About Eclipse > Installation Details > Installed Software lists "FindBugs Feature 2.0.1.20120712".
Can anyone please offer a pointer on where I'm going wrong here? Thanks!
Windows 7, Eclipse IDE for Java EE Developers Juno SR1, JDK 1.7.0_09, FindBugs 2.0.2-rc2
As suggested above, problem is likely caused by not having appropriate write access to the C:\Program Files\Eclipse\plugins folder.
Solution:
Close Eclipse. Restart Eclipse as Administrator (right click - Run as Administrator). Reinstall plugin. Restart Eclipse.
It looks like the Findbugs plugin wasn't installed properly and/or disabled by Eclipse. There can be several causes.
Multiple versions of the same plugin. To make sure this isn't the case, remove all Findbugs versions (installed manually and via the marketplace), and reinstall one (preferably via the marketplace). Watch for any warnings during installation.
There is a (dependency) conflict with another plugin. However, if this is the case I think Eclipse will warn in the log which other plugin is the cause of the conflict.
Rights problem. Make sure you have write permissions in the main Eclipse folder and all it's child folders.
I remember reading somewhere that installing Eclipse under the C:\Program Files\ in Windows can also be causing problems. Try moving Eclipse to a different folder, e.g. C:\Eclipse
Hi I also faced the similar problem but from my own experience i can suggest you the solution :-
Plz ensure that you are using eclipse version 3.6 or higher. findbugs 2.0 is not compatible with Eclipse 3.5(Eclipse Galileo).
1) Plz extract the findbugs zip file into eclipse folder(wher your eclipse is installed). This will automatically move findbug plugins into eclipse plugins folder. Restart the eclipse and you will find findbugs option on right clicking on project.
2) if 1 step does not work plz remove all the findbug jars for the eclipse plugins folder and place the complete folder into the eclipse dropins folder. Restart the eclipse and you will see the difference.
You can follow these step's to make findbugs work in your eclipse.
1.Install FireBug plugin from marketplace.
Help->Eclipse Marketplace ->then search for FindBugs
2.Configure FindBug for your project
using Maven Without Maven
This worked fine for me using eclipse juno.
I am using the STS Gradle plugin in Eclipse (Indigo). I am running on MacOSX. Eclipse is running Java 1.6, but I have Java 1.7 installed as the default JRE and all my eclipse projects use it without error.
I am trying to get "gradle jettyRun" to work within Eclipse. It runs perfectly from the command line. However, when I right click on my web project and say "Run As"->Gradle Build... then select jettyRun from the dialog box, I get this error message:
invalid source release: 1.7
Does anyone know if there is anyway to fix this?
[Don't think it matters, but I am running Gradle 1.1]
As this issue suggests, provided you're using above version 3.0.0.M1 of the STS plugin, there should be a Gradle preference page where you can select the JVM installation to use.
Not sure for earlier versions of STS plugin. You can try setting the JAVA_HOME variable before launching your Eclipse. Might help.
I have managed to track a problem where within eclipse I see no error, but anywhere outside eclipse the error exists.
The error I get when run outside eclipse is LazyInitializationException from hibernate - caused by a ${entity.service.id} reference in the jsp.
Outside eclipse I have tried jetty standalone, mvn jetty:run from the command line, and tomcat. I've cleaned the projects, disabled workspace dependency etc. I'm using eclipse galileo, m2eclipse 0.9.8.200905041414, jdk 1.6_17, maven 2.1.1 (not embedded), jetty 6.1.22 (standalone and plugin).
How is that possible??
oh my goodness. it works outside eclipse under jdk1.5.0_15 in windows, but not linux! I need it to work under linux. help!!