[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_83084 ] Baerrach bonDierne commented on MECLIPSE-192: ---------------------------------------------
Mangling occurs in ProjecTool.packageProjectArtifact(). This mangles the pom info to include the test version and then run BuiltTool.executeMaven() with the "package" phase to create the test jar. The side effect of this is to put test artifacts into D:\ide\workspace\maven\maven-eclipse-plugin\target\classes which is not good. I can see no work around for this situation except to use a different mechanism for testing. > no way to get eclipse:eclipse working since the last SNAPSHOT of the plugin > --------------------------------------------------------------------------- > > Key: MECLIPSE-192 > URL: http://jira.codehaus.org/browse/MECLIPSE-192 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Affects Versions: 2.3 > Reporter: Emmanuel Lécharny > Priority: Blocker > Attachments: maven-eclipse-plugin-bug.txt, > maven-metadata-apache.snapshots.xml, maven-metadata-central.xml, > maven-metadata-snapshots.xml > > > When trying to eclipsify Apache Directory Server project (mvn install works > fine), I get an error : > ... > Reason: Unable to download the artifact from any repository > org.apache.maven.plugins:maven-eclipse-plugin:pom:test > ... > It seems that a bad snapshot version of the plugin ahas been pushed into some > repos, and it breaks the build. > We have tried to find out what was the origin of the problem with Kenney, > unlucky so far :) > I have tried with the last 2.0.5 SNAPSHOT, same result. > I also tried to remove completely the repo, no difference, except the 5 > minutes dowloads ... > Attached : the debug trace -- 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
