An Internal Error Occurred During Updating Maven Project . Java.lang.nullpointerexception
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up An internal error occurred during: "Updating Maven Project up vote 53 down vote favorite 24 when i convert to maven project the error is : > An internal error occurred during: "Updating Maven Project". > Unsupported IClasspathEntry kind=4 what's the problem? eclipse maven share|improve this question edited Mar 9 '15 at 10:31 Matt 7,573144482 asked Aug 6 '12 at 16:58 liuzhijun 89511016 5 possible duplicate of: stackoverflow.com/questions/10564684/… –Mauno Vähä Aug 6 '12 at 16:59 2 Please take a look at this question : stackoverflow.com/questions/10564684/… –Ashutosh Jindal Aug 6 '12 at 17:06 2 thanks all,the problems was resolved. the step is :check out the project include 'src' and 'pom.xml' the my eclipse,then convert to maven project. –liuzhijun Aug 8 '12 at 1:41 1 See this question... At least it worked for me. –caarlos0 Aug 15 '12 at 19:18 add a comment| 10 Answers 10 active oldest votes up vote 127 down vote accepted This is all you need: Right-click on your project, select Maven -> Remove Maven Nature. Open you terminal, go to your project folder and do “mvn eclipse:clean” Right click on your Project and select “Configure -> Convert into Maven Project” share|improve this answer edited Nov 24 '12 at 21:51 phant0m 10.3k32258 answered Nov 24 '12 at 21:32 Alireza Mazloumi 1,507188 7 I followed all these steps, but the problem still remains! –FidEliO Jan 12 '13 at 8:10 nice, has worked for me everytime! :) –Kenny Cason May 7 '13 at 3:01 Thanks it worked just fine .. –udi May 13 '13 at 13:52 3 In STS 2.9.2 Remove Maven Nature = Disable Maven Nature. –Haim Raman Aug 21 '13 at 14:51 fyi - W
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it http://stackoverflow.com/questions/11832647/an-internal-error-occurred-during-updating-maven-project only takes a minute: Sign up An internal error occurred during: “Importing Maven projects”. java.lang.NullPointerException up vote 0 down vote favorite I am getting this error while importing a maven project in eclipse.I tried solution posted at here but didn't get issue resolved.Not sure if pom is real culprit but just adding the code below
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site http://stackoverflow.com/questions/10564684/how-to-fix-error-updating-maven-project-unsupported-iclasspathentry-kind-4 About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join https://whatiscomingtomyhead.wordpress.com/2014/02/03/delete-all-eclipse-project-related-meta-information-via-shell/ the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to fix error an internal “Updating Maven Project”. Unsupported IClasspathEntry kind=4? up vote 393 down vote favorite 119 I have imported maven project in STS, when I run update update project I receive: "Updating Maven Project". Unsupported IClasspathEntry kind=4 Is there a workaround for this? eclipse maven m2eclipse eclipse-wtp share|improve this question edited Sep 5 '12 at 11:45 GEOCHET 16.3k156085 asked May 12 '12 at 14:42 user810430 4,593132540 Does an internal error a build on command line work ? Which Maven version? –khmarbaise May 12 '12 at 18:30 1 STS - it is eclipse+plugins –user810430 May 13 '12 at 14:07 I have the same issue and i am not able to slove by this answer can you please see stackoverflow.com/questions/12049566/… –Hemant Metalia Aug 21 '12 at 7:21 add a comment| 14 Answers 14 active oldest votes up vote 599 down vote accepted This issue has been fixed in m2e 1.5.0 which is available for Eclipse Kepler (4.3) and Luna (4.4) Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=374332#c14 The problem is caused by the fact that STS (the Spring IDE/Eclipse), as well Eclipse and other Eclipse based IDE's, use the m2e(clipse) plugin but that eclipse:eclipse has been probably been run on the project. When m2e encounters a "var" .classpath entry, it throws this error. The update sites are specified at the following url: http://eclipse.org/m2e/m2e-downloads.html If you can't use m2e 1.5.0 for any reason, then : Disable the maven nature for the project (via the right-click menu) Run mvn eclipse:clean (while your project is open in STS/eclipse). Depending on the timing, you might need to do a refresh o
Main menu Skip to content HomeAbout meLicense Post navigation ← Scala Meetup Hamburg - 11. Juli2013 Telling WGET to ignore SSL-Certificates → Feb 3 2014 Delete all Eclipse project related meta information viashell Today I was fighting some really annoying behaviour of Eclipse in combination with refactored multi module maven projects. Whenever I tried to import the projects, I recieved the error An internal error occurred during: "Updating Maven Project". java.lang.NullPointerException I tried to solve the problem by removing my eclipse projects and cleaning all eclipse related files, but that didn't work. For some reason mvn eclipse:clean refused to delete my files. Thus I had to find a way to recursively delete all eclipse related information from my project. So here it is: find . -name .classpath -exec rm -rf {} \; find . -name .project -exec rm -rf {} \; find . -type d -name .settings -exec rm -rf {} \; Share this:TweetFlattrEmailLike this:Like Loading... Related By Nils Posted in Java Tagged Eclipse, Java, Maven, Shell 0 Post navigation ← Scala Meetup Hamburg - 11. Juli2013 Telling WGET to ignore SSL-Certificates → Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. About meDeveloping with Java in the ninth year now, and I am still having fun with it. Nevertheless, occasional escapades to Scala are dangerously tempting. Top Posts Absolute First Step Tutorial for Amazon Web Services Get rid of "unmappable character for encoding Cp1252" once and f