[ http://jira.codehaus.org/browse/MECLIPSE-98?page=comments#action_64147 ]
KArol Muszynski commented on MECLIPSE-98: ----------------------------------------- Maven Eclipse Plugin 2.2 works correctly with maven 2.0.2 on my environment (winxp, sdk142_10). Stephane, which maven version did You use? > Unablea to execute mvn eclipse:eclipse > -------------------------------------- > > Key: MECLIPSE-98 > URL: http://jira.codehaus.org/browse/MECLIPSE-98 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.2 > Environment: Maven version: 2.0 > Reporter: Stéphane Toussaint > > > Since maven downloaded eclipse plugin 2.2, I can't rebuild projects files. > mvn eclipse:eclipse fails with : > java.lang.NoSuchMethodError: > org.apache.maven.artifact.factory.ArtifactFactory.createDependencyArtifact(Ljava/lang/String;Ljava/lang/String;Lorg/apache/maven/artifact/versioning/VersionRange;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Z)Lorg/apache/maven/artifact/Artifact; > at > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.createManagedVersionMap(AbstractIdeSupportMojo.java:625) > at > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution(AbstractIdeSupportMojo.java:408) > at > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:378) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:452) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Is this matters with the plugin itself or by another dependency ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
