You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:45:08 UTC

[jira] [Closed] (MRELEASE-517) Release should have parameters to update the parent pom and then resolve dependencies appropriately

     [ https://issues.apache.org/jira/browse/MRELEASE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-517.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Release should have parameters to update the parent pom and then resolve dependencies appropriately
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-517
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-517
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.0-beta-9
>            Reporter: Kurt Zettel
>
> The maven-versions-plugin will update my project's parent pom version to the latest release version.  It would be nice if the release plugin would do the same. I am currently unable to find a way to use these two plugins together to automate a release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)