You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lars Corneliussen (JIRA)" <ji...@codehaus.org> on 2010/06/08 11:35:12 UTC

[jira] Commented: (MRELEASE-554) Allow custom files to be modified before doing a prepare or branch...

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

Lars Corneliussen commented on MRELEASE-554:
--------------------------------------------

Do you accept git-patches? This would make it much easier, because git can't really generate patches that are readable for svn.

You could use git-svn or the apache git-mirror to apply them.

> Allow custom files to be modified before doing a prepare or branch...
> ---------------------------------------------------------------------
>
>                 Key: MRELEASE-554
>                 URL: http://jira.codehaus.org/browse/MRELEASE-554
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: branch, prepare
>    Affects Versions: 2.0
>            Reporter: Lars Corneliussen
>            Priority: Minor
>
> I want to call 'versions:update-parent' and 'versions:update' before I do a release preparation. This should not be a separate commit, but in the 'prepare release' commit.
> In conjunction with MRELEASE-458 (create branch/tag from working copy, no commits to working copy) this allows for releases without touching the working copy. This is useful in cases where the release is created from a tag or where the trunk should not move forward to a new development version.
> I'm working on a patch that I will attach when it is done.

-- 
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