[
http://jira.codehaus.org/browse/MRELEASE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218070#action_218070
]
Dennis Lundberg commented on MRELEASE-547:
------------------------------------------
For every release of Maven the super POM is given a look through to see if
there are any plugins that needs to be upgraded. An upgrade will only occur if
the new plugin version has been tried and tested successfully in a real world
environment. So no, plugins are not automatically upgraded - it's a manual
process.
> Wrong version (2.0-beta-8) downloading from repo
> ------------------------------------------------
>
> Key: MRELEASE-547
> URL: http://jira.codehaus.org/browse/MRELEASE-547
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.2.1, Windows, Java 1.6
> Reporter: Edward Staub
>
> (This probably isn't a problem with the plugin itself - but I'm not sure, and
> can't think where else to post.)
> When I try to run
> mvn release:update-versions
> I'm getting 2.0-beta-8, when I should get 2.0 according to both <latest> and
> <release> in the metadata.
> The "update-versions" target isn't even in beta-8, so it blows up.
> I can't get the correct version of the release plugin to download from the
> the repository.
> I can't find any dependencies that point at beta-8 in my local repo.
> If I try to use the update-versions goal, I get the WRONG version.
> But if I run the help:describe target on the release plugin, it fetches the
> RIGHT version, 2.0.
> I haven't touched settings.xml.
> I get this behavior even in a directory with no POM, so I know it's not being
> trigger by something in the POM.
--
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
