You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2010/02/01 19:37:55 UTC

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

    [ http://jira.codehaus.org/browse/MRELEASE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208826#action_208826 ] 

Wendy Smoak commented on MRELEASE-517:
--------------------------------------

You could try using the scm plugin to commit the changes made by the versions plugin.

(Probably best to discuss on the mailing list, JIRA isn't great for that sort of thing.)

> Release should have parameters to update the parent pom and then resolve dependencies appropriately
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-517
>                 URL: http://jira.codehaus.org/browse/MRELEASE-517
>             Project: Maven 2.x 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 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