[ http://jira.codehaus.org/browse/MNG-527?page=all ]
Brett Porter updated MNG-527:
-----------------------------
Fix Version: 2.0-beta-1
> Attempt to determine Plugin RELEASE version fails when managed by second
> pluginRepository
> -----------------------------------------------------------------------------------------
>
> Key: MNG-527
> URL: http://jira.codehaus.org/browse/MNG-527
> Project: Maven 2
> Type: Bug
> Versions: 2.0-alpha-3
> Environment: WinXP SP2, Java 1.5, Maven 2.0-alpha3
> Reporter: John Fallows
> Fix For: 2.0-beta-1
>
>
> Consider the case where two <pluginRepository> elements are present in
> pom.xml, and a particular plugin is being stored in the second plugin
> repository.
> During a build, say m2 install, plugin versions are being automatically
> checked to see if a more recent release version is available. This causes a
> request to be made for the RELEASE.txt file in the plugin repository.
> Since the plugin in question is not stored in the first plugin repository,
> this request for RELEASE.txt fails.
> However, instead of continuing to process the second plugin repository, the
> build fails.
> Of course, reversing the order of the <pluginRepository> elements in pom.xml
> can resolve the issue, but then a different set plugins would fail during
> automatic update.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
