[jira] Commented: (MNG-5084) Resolver for plugins failing

["Mark Derricutt (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272435#comment-272435 ] 

Mark Derricutt commented on MNG-5084:
-------------------------------------

Swapping our aether 1.11 for 1.12 in my maven/lib directory seems to solve this problem.  After removing settings.xml and clearing out .m2/repository maven would fail the IT tests with 1.11, 1.12 works as expected.

What would it take to propose a 3.0.4 release of maven with the newer aether included?


> Resolver for plugins failing
> ----------------------------
>
>                 Key: MNG-5084
>                 URL: https://jira.codehaus.org/browse/MNG-5084
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0.3
>         Environment: JDK 1.6.24, Mac OS X
>            Reporter: Richard Vowles
>            Priority: Critical
>         Attachments: Screen shot 2011-05-12 at 10.43.05 PM.png, simple-plugin.tar
>
>
> We are at a standstill with the easyb plugin for maven as we cannot get it to resolve artefacts when doing its integration tests. Installing it without them and then using it also fails with resolution problems. 
> I downloaded the source and did a remote debug, the resolution seems to *require* that the artefact that is missing be deployed locally, even if these artefacts are in central and are listed in the _maven.repositories file as being from central. It seems to be looking for them as groovy-all-1.7.10.jar>= (for example) even when there is a groovy-all-1.7.10.jar>central= and it has previously just downloaded it from central.
> I have created a trivial sample, that builds nothing but has an integration test (which also fails). To reproduce, you need to have *no* settings.xml and clear your repository out (rename it to something else) so you have what appears to be a bare repo. Then run a mvn clean verify (using 3.0.3) and it builds, installs the plugin, runs the integration test and fails. If you edit the integration test and specify the version and mvn clean verify again, it still fails (so it has nothing to do with the invoker plugin).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira