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/05/05 17:25:12 UTC
[jira] Created: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
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
[jira] Commented: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRELEASE-554:
----------------------------------
Patch Submitted: [Yes]
Fix Version/s: 2.1
patch to review
> 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
> Fix For: 2.1
>
> Attachments: MRELEASE-554-custom-modified-files.patch
>
>
> 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
[jira] Issue Comment Edited: (MRELEASE-554) Allow custom files to
be modified before doing a prepare or branch...
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220046#action_220046 ]
Lars Corneliussen edited comment on MRELEASE-554 at 6/8/10 4:32 AM:
--------------------------------------------------------------------
Browse the current changes.
http://github.com/lcorneliussen/maven-release/commit/4aded50ff82d4805fbc7ea9ec775f368588c5ebd
was (Author: lcorneliussen):
Browse the current changes.
http://github.com/lcorneliussen/maven-release/commit/4aded50ff82d4805fbc7ea9ec775f368588c5ebd
Patch with tests to come.
> 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
[jira] Commented: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220046#action_220046 ]
Lars Corneliussen commented on MRELEASE-554:
--------------------------------------------
Browse the current changes.
http://github.com/lcorneliussen/maven-release/commit/4aded50ff82d4805fbc7ea9ec775f368588c5ebd
Patch with tests to come.
> 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
[jira] Closed: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-554.
---------------------------------
Resolution: Fixed
Assignee: Brett Porter
applied, thanks!
> 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
> Assignee: Brett Porter
> Priority: Minor
> Fix For: 2.1
>
> Attachments: MRELEASE-554-custom-modified-files.patch
>
>
> 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
[jira] Updated: (MRELEASE-554) Allow custom files to be modified
before doing a prepare or branch...
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-554:
---------------------------------------
Attachment: MRELEASE-554-custom-modified-files.patch
Allows for configuration of user-defined local modifications that will be accepted during a release:perform.
____________
Based on r983489 in https://svn.apache.org/repos/asf/maven/release/trunk
Online Compare: http://github.com/lcorneliussen/maven-release/compare/473197249e1caf39ee2cee6d0efc8a288c30d0c3...1b0672d1050a9c100cde4e1b788d5126ea8468f3
h4. Included commits:
- [MRELEASE-554] Allow custom files to be modified before doing a prepare or branch
o Bumped the release-descriptor.mdo to version 2.1
o Both 'prepare' and 'branch' now have a configuration value checkModificationExcludes/checkModificationExcludeList (by Lars Corneliussen<me...@lcorneliussen.de> on 05.05.2010 18:57:18)
Generated from http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/tree/MRELEASE-554-custom-modified-files
> 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
> Attachments: MRELEASE-554-custom-modified-files.patch
>
>
> 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