I downloaded lombok.jar (lombok-1.16.14.jar) put it into my Downloads. Then I clicked on this jar, the execution correctly identifies the Eclipse instances on my MacOS and then I selected the instance I want. Lombok is also specified in the pom.xml
org.projectlombok
lombok
1.16.14
provided
In eclipse.ini I got the addition:
-javaagent:../Eclipse/lombok.jar
lombok.jar was added to the same directory as eclise.ini
/Applications/Eclipse.app/Contents/Eclipse
I am still getting setter/getter errors in Eclipse Problems despite that my mvn build works fine.
The code for a User:
#Entity
#Getter
#Setter
#NoArgsConstructor
#AllArgsConstructor
#EntityListeners(UserListener.class)
public class User implements Serializable, UserDetails {
...
The error:
The method getRole() is undefined for the type User
Since you have already added the .jar to your lib folder, then go to the lib
and execute java -jar lombok-1.16.4.jar, you'll see a wizard, specify the location of your eclipse.ini, after you are done with this your eclipse.ini file should look like this:
-vmargs
...
-javaagent:lombok.jar
-Xbootclasspath/a:lombok.jar
For me this just worked fine but I found in other answers that:
You should not just "restart" Eclipse, go to File -> Exit and then open it again. taken from here
Don't forget to do a mvn clean just to make sure that you recompiled your classes. taken from here
After all this you should also right-click on your project, then Maven -> Update Project taken from here
There is a manual way to install lombok under eclipse, I do not checked it, but it maybe helps you -
copy lombok.jar to where your eclipse folder where is the eclipse.ini
open eclipse.ini，put at end the below two lines below and save it
-Xbootclasspath/a:lombok.jar
-javaagent:lombok.jar
restart eclipse.
I had the problem, that the link, which I used to start eclipse, didnt respect the eclipse.ini file.
My environment is:
IDE: Version: Neon.0 Release (4.6.0)
OS: Ubuntu 16.04.2 LTS
The installation routine java -jar lombok-1.16.16.jar works quite well. I.e. it adds the reasonable line -javaagent:<ABSOLUTE_PATH_TO_ECLIPSE_INSTALLATION>/lombok.jar to the eclipse.ini.
But if I start eclipse by using my desktop-shortcut, it starts without lombok (checked by looking at "Help"->"About Eclipse").
If I start eclipse by executing the executable eclipse next to the eclipse.ini file, lombok launches like a charm.
Hence I checked my desktop shortcut (e.g. ~/.local/share/applications/eclipse.desktop) and indeed, it started eclipse without reflecting the eclipse.ini.
Instead it uses something like /usr/bin/java -jar org.eclipse.equinox.launcher.jar ... to start eclipse.
So the solution was to replace the old Exec line in the desktop shortcut by:
Exec=/opt/eclipse/neon/eclipse
where /opt/eclipse/neon/ is the place where I have installed eclipse.
Antoniolazaro has given a solution for Eclipse Neon issue on MacOS
When I put the complete path, it works on Mac Os.
-javaagent:/Applications/Eclipse.app/Contents/Eclipse/lombok.jar
Resource Link:
https://github.com/rzwitserloot/lombok/issues/1173
And the lombok project owner rzwitserloot has given 3 suggestions for checking
Can you give us the complete path, from root, of your eclipse
install? Starting with 1.16.14, the installer should still find
eclipse even with the funky paths that the OOM installer comes up
with. I have no idea why the installer isn't finding your eclipse
automatically, here. I can't reproduce this on my mac.
The lombok uninstaller has the same 'find eclipses' capability as
the installer. Mac doesn't have a registry and we aren't going to
dump a bunch of crud in your homedir just to keep track of where we
installed your lombok; we like it that way: No cruft. So, that part
(that the uninstaller can't find a custom-install location and
requires you to again specify it) is not a bug.
You still have to add lombok.jar to your project as a dependency
same as any other third party dependency (something like guava, for
example). It's not clear from your problem description if you
actually did that.
Resource Link:
https://github.com/rzwitserloot/lombok/issues/1310
Even after following the below steps(try the steps given below first) , if it doesn't works, one issue can be that you are using the eclipse from the desktop , not from the folder where eclipse is installed. Running eclipse from the desktop sometimes is unable to load the .ini file, hence lombok won't run. So, try running the eclipse from the folder where you have installed it.
Steps:
1. Give the lombok dependency in the pom and build it.
The lombok.jar is usually downloaded in the folder .m2/repository/org/projectlombok/lombok/1.x.y
Install the jar in the folder "java -jar lombok-1.x.y.jar"
Then it will ask you to select the IDE. Browse to the eclipse installation
folder and select eclipse from there.
Now your eclipse installation folder, should contain the lombok.jar and eclipse.ini should contain the line
-javaagent: /lombok.jar
Run the eclipse from the installation folder. Clean and rebuild the project.
It should work now!
try #Data annotation for the class.
public #Data class user{
\\do stuff
}
For me, downloading the latest Eclipse Neon, i.e. Neon 3, fixed the problem
My environment is:
IDE: Version: Neon.3 Release (4.6.3)
OS: Ubuntu 16.4
It works for me when i do this steps below:
1. copy `lombok.jar` to where your eclipse folder where is the `eclipse.ini` ;
2. open `eclipse.ini`，put at end the two lines below with full lombok path and save it：
-Xbootclasspath/a:/DEV/Tools/IDE/eclipse/jee-neon/lombok.jar
-javaagent:/DEV/Tools/IDE/eclipse/jee-neon/lombok.jar
3. restart `eclipse` in command line (when i try run with exist link in launcher it's not work)
4. rebuild your projects
As far as I am concerned, I use a "Chocolatey" distribution of Eclipse on Windows.
It does not change much. But for those of you who are not admin of their desktop, it might be a hassle, because Chocolatey installs softwares in C:\ProgramData\... which is an "admin" directory.
In other words, you may need to modify your shortcut's property "start in" which will not be possible unless you are admin of your desktop.
The trick that worked for me here was to create a new shortcut, which has the correct "start in" property to start eclipse in the directory where the eclipse.ini is...
Then recompile using eclipse, then work on your project a bit until eclipse realizes that lombok was installed...
Cheers
After installing lombok, you need to copy lombok.jar into your project or add dependency in maven configuration xml file
exit the eclipse and then go to the eclipse directory and open eclipse.ini and add -clean on a top and rerun the eclipse. hope your problem is solved.
To elaborate on the above replies:
PROBLEM:
In my scenario:
I installed SpringBoot STS under Eclipse Photon,
I created aSpring Boot/Gradle build project, and I got the "undefined method" error using Lombok #Data.
Environment: Ubuntu Linux 18.04.
SOLUTION:
cd ~/.gradle/cache/.../lombok/...;
java -jar lombok-1.16.22.jar
NOTE:
java -jar lombok*.jar brings up a GUI that
Allows you to select which Eclipse install to update.
Updates eclipse.ini AND...
Copies lombok-xyz.jar into the Eclipse install folder, as lombok.jar.
Eventhough there are already a lot of answers here none of the given answers solved my problem, so I'll add my information here as well in case it might help someone:
My setup is:
Win10 Home,
Eclipse Version: Oxygen.3a Release (4.7.3a),
Eclipse Build id: 20180405-1200,
Add lombok to my pom.xml
mvn clean install
close eclipse
navigate to my .m2 folder .m2\repository\org\projectlombok\lombok\1.18.6>
run: java -jar .\lombok-1.18.6.jar (or whatever version you have
Install lombok
Now it's getting intresting. The installation added the following to my eclipse.ini:
-javaagent:lombok.jar
How ever it placed them at the bottom of my .ini file. So it looked liked this.
--launcher.appendVmargs
-vmargs
-...
--add-modules=ALL-SYSTEM
-javaagent:lombok.jar
I assumed that -javaagent:lombok.jar belongs under -vmargsso I put it at the bottom of --launcher.appendVmargs. That didn't work either though. But when I put -javaagent:lombok.jarright below vmargs it works. Ultimately my eclipse.ini looks like this:
--launcher.appendVmargs
-vmargs
-javaagent:lombok.jar # lombok works for me if this is here
-Declipse.p2.max.threads=10
- Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
#-javaagent:lombok.jar | lombok doesn't work for me if its placed here.
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
Not sure why this issue orcurrs but maybe it helps you. If you are under macOS remember to add -Xbootclasspath/a:lombok.jalike other answers in this thread suggest.
I have faced this issue recently and all the above solutions mentioned by the above users didn't work. The problem I have was there are special symbols like '$' in path(This can be found in last line of eclipse.ini file) to eclipse. Due to the same reason lombok cannot identify the file and append the necessary two lines in eclipse.ini file. Removing the special characters like '-' , '$', '_' in my eclipse path fixed mu problem
For, after installing lombok like mentioned above I had to do right click on your project folder -> Run as -> Maven clean. Ne the .jar is deteced and properly used
Copy and paste the lombok jar into the eclipse installation folder.
Run the command "java -jar lombok-.jar".
A GUI opens.
Check the IDE listed in the installer.
This entry should be available in the eclipse.ini file "-javaagent:<>".
Restart Eclipse to find the changes which starts listing the associated getters, setters in your java file.
Simply add to eclipse.ini file this statement (or check if you have):
-Xbootclasspath/a:lombok.jar
-javaagent:lombok.jar
Attention please, usually you have only:
-javaagent:lombok.jar
Obviously restart your eclipse
For Eclipse neon on Mac (High Sierra) :
Use lombok version 1.16.14 or above.
Installer launches by running (double clicking) lombok-1.16.14.jar file itself. It should detect installed versions.
On the Mac, it detects Eclipse.app only from Applications directory. If not, you can tell the jar where to find it in the popup dialog. Note that you should point it to eclipse.ini file (Eclipse.app -> Show app contents -> eclipse -> eclipse.ini)
Lower versions of lombok do not work on High Sierra. They don't detect installed eclipse instances.
Finally remember to restart eclipse (via File -> exit) and run maven update project.
I might be late to reply here but for future references adding this answer,
Please don't use Lombok v1.18.14 as it will crash eclipse. It is mentioned in changelogs. Use next version v1.18.16.
Simple way to setup lombok to eclipse is mentioned in this answer https://stackoverflow.com/a/69332138/3637115
I have a maven project which I have downloaded from this link. When I make a couple changes to it, it runs perfectly from the command line when I type:
mvn clean install tomcat7:run-war -Dmaven.test.skip=true
in the directory to which the zip was extracted. (The only 2 changes required to make it work on the command line are to 1.) add a plugin tag for tomcat 7 in pom.xml and 2.) create a context.xml file in the webapp/META-INF folder. Everything else in the app remains the same as the github verion, and the app runs fine from the command line using the command given above and then typing the url in the browser.)
However, when I import the project into eclipse as an existing maven project, and then try to run the app, the app starts throwing errors related to not finding a couple of jars which are clearly in the repository. The app no longer compiles from the command line, or from eclipse. I even tried to run the app as a maven build from eclipse and even changed the maven instance eclipse uses to the freestanding maven that works from the command line instead of the embedded maven in eclipse, but the app still threw the same errors when I tried to run it.
But then, when I repeated the steps with a fresh copy of the app, the fresh copy runs fine from the command line, while the copy that eclipse touched does not compile by any method.
It seems that eclipse has made some changes to the app in the process of importing it as an existing maven project into eclipse. How can I locate the specific changes that eclipse has made to the app? I would like to be able to use eclipse as my IDE, but I cannot do so unless it can compile the code.
This answer was originally posted as a comment it turns out that resolved the OP's problem, and as He asked I'm turning into an answer.
First set your eclipse to use the JDK instead of the JRE. Just as a reference this configuration on Eclipse is Normally on Window->Preferences...->Java->Installed JREs:
Second (as you already did) change eclipse maven to look at installed maven that runs on the command line again.
I've encountered some problems with maven running with the JRE instead of the JDK. Try it and let me know. I will sleep now. Tomorrow I will see what happened.
I have a repository in which I have a simple ant project (only the src directory and the build.xml file). I did a checkout of this project in a local copy. Then I opened Eclipse, created a "Java Project from existing Ant build file" and it worked fine. I can build, clean, run, generate javadocs, etc. However, my problem is that the source files in the packages, as well as the project itself, doesn't appear to be under version control in Eclipse. I can work with it fine from Cygwin, but not from the GUI.
The odd thing is that I have several regular Java projects, on the same repository which are synced fine by Eclipse, so it's not a version issue.
When I created the projects that work, I had to go to Team->Share Project... and Eclipse told me that they were already under version control and updated its configuration. However, in this current case, this isn't working. Any suggestion please?
EDIT:
I'm using svn 1.8.
UPDATE: I tried creating a regular Java project, and this time the version control looks fine, so it appears it's an issue related only to Java Project from Existing Ant build file.
The problem is that Eclipse doesn't know your project is using Subversion as a version control tool. You did a checkout outside of Eclipse, then you set up Eclipse as if this was a non-version controlled project.
To get Eclipse to recognize the project as under Subversion, you need to let Eclipse know. This means you should have said "File->New->Project, and select SVN->Checkout Project from SVN in the new project wizard. Then, Eclipse would have checked the project out in Subversion for you, and Eclipse would understand this project is in Subversion.
Unfortunately, I am not quite familiar enough with Eclipse to know how to tell Eclipse that the current project is really under version control. The best I could come up with was:
Right-click on the project and select Team->Share
Say this is a Subversion project you want to share.
Select the Repository to use
Select the folder where you want this project, and select the current folder.
You get the following warning:
Warning: The specified folder already exists in the repository. If you continue, that folder will be checked out to the existing location. Do you want to continue?
Your project will now be "checked out" over your current project. Everything should be okay because the files you have either match what is in Subversion or are modified versions of what is in Subversion.
You will be then asked to use the Synchronized view. Check "Yes", and then switch back to the Java view. Eclipse will now know your project is under Subversion and everything should work fine.
Note the use of Shoulds and Coulds. This is my way of saying that the advise given is done on an "as is" basis and I am not responsible for any damage done by following this advice, so please don't sue me.
It's basically your standard open source license.
I exported my eclipse plugin through the "Export Wizard" in the manifest and seems like everything went well (no errors). It created a .jar file within a plugin directory in a zip file.
I thought putting the jar into my Eclipse plugin directory would install it (after re-launching eclipse) but that didn't work. Eclipse can't see the plugin (the perspective isn't showing up)
I tried with Help->Install new software->local archive but it keeps saying "no software found"
Can you help me getting my plugin ready to be installed on a fresh Eclipse copy?
Ps. my plugin uses other dependencies like EMF/GMF
In eclipse, go to your console window. From the drop down meny, select OSGI console. Run the command ss or ss <name of your plugin>
You will then see the state of your plugin and a number. The state will probably be "installed" which means if has been found, but some dependencies were not satisfied.
Run the command diag <number of your plugin> and you will see why it wasn't started.
For more details, see Wheres my bundle
Edit: A first step to verify that the plugin is working would be to start up a new eclipse instance with your plugin. In the run configuration dialog, there is a tab with all the plugins that should be started. Make sure yours is checked and it will start with the new eclipse instance.
If you are using Eclipse 3.4 or above, put your plugin in the 'dropins' directory.
To install via Help->Install new software you need to create an 'Update site' or a 'p2 repository'.
By far the most ellaborate descriptions of installing your plugin is provided by Vogella deployment of your plug-in
It covers all 3 possible ways in which you may install your plugin detailing the pros & cons of each of the following approaches :
1 . Installing your plug-in from your Eclipse IDE
2 . Export plug-in and put into dropins folder
3 . Create update site for your plug-in
Sometimes you just have to restart Eclipse. File -> Restart and try again. Worked for me because Eclipse was caching the results of my local update site.
Open plugin.xml
In "Overview" Tab in "Exporting section" go to "Export Wizard"
In "Export" window in "Destination" section choose "Install into host. Repository" and choose dir which will looks like "xxx/.metadata/.plugins/org.eclipse.pde.core/install/"
Press "Finish" button
Wait for Export to finish without any problems
Restart Eclipse
I am trying to install PMD onto my Eclipse Helios installation. I follow the usual instructions to use the 'Install New Software' feature within Eclipse. All seems to go swimmingly and the installation completes. After restarting Eclipse, the option to use PMD is not there as expected (by right-clicking on a project).
Could someone advise on any steps I may have missed? Eclipse is the 20100617-1415 version installed on Red Hat running KDE.
Any guidance will be appreciated.
Thanks
Either the PMD plugin had an error on installation, or there was a problem when trying to start the plugin up. Either way, there should be something in your error log.
I'd first check there to see if something relevant in the log (open the Error log view). If not, then you can check to see if the plugin is actually installed. Click on Help -> About Eclipse -> Installation Details -> plugins and look for PMD.
If it is installed, then try uninstalling and reinstalling it. If the PMD plugin is not installed, then something failed.
Make sure that your eclipse/ directory is writable for the current user (while not a hard requirement, many plugins do need this for some reason).
Unfortunately it is not possible to install PMD from the Eclipse Marketplace.
Only way: Help > Install New Software... > Add... > http://pmd.sourceforge.net/eclipse
Maybe you have installed eclipse-pmd instead of PMD. It'll be avalible only in the project's properties option.
You can better try to install from http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/
But, make sure the Window-Preferences-General-Network Connection is "Direct" and "Native".
And restart. You'll surely find the PMD in preferences. I did for Keplar and works fine.
To install the PMD plugin for Eclipse:
Start Eclipse and open a project
Select "Help"->"Software Updates"->"Find and Install"
Click "Next", then click "New remote site"
Enter "PMD" into the Name field and
"http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/"
into the URL field
Click through the rest of the dialog boxes to install the plugin
To configure PMD, select "Windows"->"Preferences", then select PMD.
To run PMD, right-click on a project node and select "PMD"->"Check code with PMD".
For more info refer LINK