As the title mentioned I have the following problem: I use Eclipse
with Maven Nature
and when I update my Maven Project, I get this error:
An internal error occurred during: "Updating Maven Project".
Unsupported IClasspathEntry kind=4
The solution that always comes back is the following:
mvn eclipse:clean
(with project open in eclipse/STS)mvn eclipse:eclipse
next)Now I exhaustively tried all combinations several times. But I always keep getting the above error. The error starting occurring when I had to mvn eclipse:eclipse
the project. Before it was always running fine using only m2eclipse features and setting everything in eclipse.
It helped in my case
rightclick project, remove maven nature
mvn eclipse:clean
(with project open in eclipse/STS
)
delete the project in eclipse (but do not delete the sources)
Import existing Maven project
I solved this by looking at this comment on JBIDE-11655 : deleting all .project, .settings and .classpath in my projects folder.
Slightly different option usually works for me:
That's all, no need to re-import but need to have the terminal window handy.
I imported the project as general project from git repository.
.settings
, .project
and .classpath
in project's folder Configure -> Convert to Maven Project
. Only this solved the problem in my case.I have that problem and my solution is going source folder and run command line: mvn clean install -DskipTests eclipse:eclipse then return eclipse workspace and refresh project. Hope that help!
After trying all these procedures it still didn't work for me. What did work was
Our current work required integrating a number of disparate projects so unfortunately use of SNAPSHOTs in a production environment were required (taboo in Maven circles)!
Your command line mvn eclipse project generator may not be the same version as that of your eclipse, and eclipse doesn't understand for your command line tool is generating. Just use eclipse's in this case:
rm -rf .settings/ .project .classpath
to delete eclipse project files, also from modules I just went to Properties
-> Java Build Path
-> Libraries
and removed the blue entries starting with M2_REPO.
After that, I could use Maven
-> Update Project
again
My tricky solution is:
Maven -> Update Project
again. Issue is resolved.
If you have Tomcat Server Running in Eclipse, you need to refresh project before restart Tomcat Server.
This issue (https://bugs.eclipse.org/394042) is fixed in m2e 1.5.0 which is available for Eclipse Kepler and Luna from this p2 repo :
http://download.eclipse.org/technology/m2e/releases/1.5
If you also use m2e-wtp, you'll need to install m2e-wtp 1.1.0 as well :
I removed my .classpath
file in my project directory to correct this issue. No need to remove the Maven Nature from the project in Eclipse.
The specific error I was getting was: Project 'my-project-name' is missing required Java project: 'org.some.package-9.3.0 But my project wasn't dependent on org.some.package
in any way.
Perhaps an old version of the project relied on it and Maven wasn't properly updating the .classpath
file.
This is all you need:
Right-click on your project, select Maven -> Remove Maven Nature.
Open you terminal, navgate to your project folder and run mvn eclipse:clean
Right click on your Project and select Configure -> Convert into Maven Project
Right click on your Project and select Maven -> Update Project
Source: Stackoverflow.com