An internal error occurred during: "Updating Maven Project". Unsupported IClasspathEntry kind=4
Solution 1
I had to do it slightly different to work for me:
- rightclick project, remove maven nature (or in newer eclipse, "Maven->Disable 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
Solution 2
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
Solution 3
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
Solution 4
After trying all these procedures it still didn't work for me. What did work was
- go into File Explorer and delete the .classpath file under the project's root folder
- run Maven update within Eclipse, and check Force update of Snapshots/Releases
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)!
Solution 5
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 :
![Vjeetje](https://i.stack.imgur.com/WcFiv.png?s=256&g=1)
Vjeetje
Updated on June 25, 2020Comments
-
Vjeetje about 4 years
As the title mentioned I have the following problem: I use
Eclipse
withMaven Nature
and when I update my Maven Project, I get this error:An internal error occurred during: "Updating Maven Project".
Unsupported IClasspathEntry kind=4The solution that always comes back is the following:
- rightclick project, remove maven nature
mvn eclipse:clean
(with project open in eclipse/STS)- (sometimes they suggest to do
mvn eclipse:eclipse
next) - rightclick project and reenable maven nature
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. -
Aritz about 11 yearsNot necessary to remove maven nature at all.
-
Adrian Ber over 10 yearsInstead of 3 I deleted the .settings folder and refresh the project in Eclipse and instead of 4 I did Configure > Convert to Maven project.
-
slash33 over 10 yearsStep 2 removed .classpath and .project even when the project was opened in Eclipse Juno.
-
erhun about 10 yearsIt is working with an extra Maven->Update Project at the end of this steps. Thanks.
-
NikhilWanpal over 9 years@JJZabkar Probably this will help: stackoverflow.com/questions/10564684/…