Monday, July 29, 2013

Maven vs. Eclipse: An internal error occurred during: "Importing Maven projects". Unsupported IClasspathEntry kind=4


I had this kind of problem twice while trying to import a Maven project using Eclipse.
One using mvn command and the other using the option File, Import, Existent Maven Projects.
Check which one is your's.
Usually this kind of problem happens due to unicode issues.


1.  USING File, Import, Existent Maven Projects


>PROBLEM

You the get the warning when trying to import the maven project.



 >SOLUTION

 Delete the folder and files shown on the picture below and import the project again.








2.  USING mvn COMMAND

Problem

Importing by Eclipse a project created using maven commands, as follows:
mvn archetype:generate
...
cd project_root
mvn eclipse:eclpse

generates the message above.

Follow the details by the pictures below.

Solution

Use just the "mvn archetype:generate" command and then go straight to the Eclipse's import, without using "mvn eclipse:eclipse".



Step by Step the Import Failure 







No comments:

Post a Comment

virtualbox6: debian: netbeans install issues: "dpkg: warning: 'ldconfig' not found in PATH or not executable" and "pkg-deb: error: archive 'apache-netbeans_....deb' uses unknown compression for member 'control.tar.zst', giving up"

  >PROBLEMS/SOLUTIONS You desire to install  Netbeans  on a Debian O.S. using the VirtualBox v.6 because the VirtualBox v.7 fails on your...