[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_83077 ]
Baerrach bonDierne commented on MECLIPSE-192:
---------------------------------------------
Ok.
In AbstractJarMojo.java line 152:
{code:language=java}
archiver.getArchiver().addDirectory( contentDirectory, DEFAULT_INCLUDES,
DEFAULT_EXCLUDES );
{code}
where
contentDirectory =
D:\ide\workspace\maven\maven-eclipse-plugin\target\classes
This directory contains the mangled plugin.xml
D:\ide\workspace\maven\maven-eclipse-plugin\target\classes\META-INF\maven\plugin.xml
Now to work out who mangles it and how to fix it.
> 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
