[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_82929 ] 
            
Baerrach bonDierne commented on MECLIPSE-192:
---------------------------------------------

I am still getting this issue for the latest version on trunk, revision 488511

The culprit unit tests are these ones (I isolated them by placing excludes in 
the maven-surefire-plugin configuration:
{noformat}
            
<exclude>org/apache/maven/plugin/eclipse/EclipsePluginTest.java</exclude>
            
<exclude>org/apache/maven/plugin/eclipse/RadPluginTest.java</exclude>
            
<exclude>org/apache/maven/plugin/eclipse/EclipsePluginMasterProjectTest.java</exclude>
{noformat}

They cause the META-INF\maven\plugin.xml to have an incorrect version tag.
Instead of 
{noformat}
  <version>2.3-INTERNAL-r488130-pMECLIPSE-206</version>
{noformat}
it is
{noformat}
  <version>test</version>
{noformat}

I'm still investigating this and will provide more details later.
In the mean time, can this issue be re-opened please.

> 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


Reply via email to