maven-eclipse-plugin (eclipse:eclipse) and m2e are not compatible,you should not use the first one anymore.Remove the project from workspace, delete the .project,.classpath and .settings files and reimport as existing maven project, and it will be better.
On Thu, Jun 6, 2013 at 10:21 AM, Hans Wurst <chon...@gmx.net> wrote: > Hi! > > I'm new to Maven and web service programming but will have to deal in the > future. I have the source code of an web app developed by another company. > According to their install instructions I should set up Eclipse with SVN > and Maven integration. I get the project into Eclipse by creating a new > project from SVN. Then I run mvn eclipse:eclipse from the command line to > create the projects settings (with project closed in Eclipse during that > operation). After that I open the project again and enable the Maven > nature. There I'll get the following error message: > > An internal error occurred during: "Enabling Maven Dependency Management". > Unsupported IClasspathEntry kind=4 > > The mvn eclipse:eclipse command seems to create a "wrong" .classpath file. > One of my collegues was able to get this shitty project working but he > isn't sure what trick was doing the magic to get it running. His .classpath > file differs a lot from the one that maven creates on my machine. My > entries look like: > <classpathentry kind="var" > path="M2_REPO/javax/activation/com.springsource.javax.activation/1.1.1/com.springsource.javax.activation-1.1.1.jar" > sourcepath="M2_REPO/javax/activation/com.springsource.javax.activation/1.1.1/com.springsource.javax.activation-1.1.1-sources.jar"/> > whereas his are more of this type: > <classpathentry kind="var" > path="M2_REPO/javax/activation/com.springsource.javax.activation/1.1.1/com.springsource.javax.activation-1.1.1.jar" > sourcepath="M2_REPO/javax/activation/com.springsource.javax.activation/1.1.1/com.springsource.javax.activation-1.1.1-sources.jar"> > <attributes> > <attribute > name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/> > </attributes> > </classpathentry> > This is the only difference I found so far. Cleaning via mvn eclipse:clean > is not making any difference. What am I doing wrong? > The code of the other company is a mess. Is there anything I have to > consider when creating a Maven project in Eclipse from existing sources? > I'm using a Mac (Mountain Lion 10.8.3) with Eclipse Juno (m2e - Maven > Integration for Eclipse 1.3.1.20130219-1424 > org.eclipse.m2e.feature.feature.group). When I check the Maven version on > the command line I get: Apache Maven 3.0.4 (r1232337; 2012-01-17 > 09:44:56+0100). Java_home is jdk1.7.0_17.jdk in Eclipse and on command > line. Help would be really appreciated as I'm struggeling to get this mess > working at all. Thanks! > > regards > Bjoern > > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/m2e-users > > -- Adrien Rivard
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
