[
http://jira.codehaus.org/browse/MRELEASE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90245
]
Joerg Buchberger commented on MRELEASE-203:
-------------------------------------------
- WORKAROUND:
specify version only in root POM to avoid version tag adaption hell, because
only one version tag needs to be incremented to prepare for next iteration
> support more than one release pattern via new goal release:branch
> -----------------------------------------------------------------
>
> Key: MRELEASE-203
> URL: http://jira.codehaus.org/browse/MRELEASE-203
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5, 2.0
> Environment: irrelevant
> Reporter: Joerg Buchberger
>
> - CURRENT BEHAVIOUR:
> maven currently seems to support only this one release pattern well:
> *_feature branches_*
> develop towards release in trunk; prepare it by tagging, then release from
> that tag; continue for next iteration in trunk (+pom version tags are nicely
> updated+), while some or most features are done in branches
> - DESIRABLE IMPROVEMENT:
> alternative patterns or customizations such as *_release branches_* should be
> available:
> develop features in trunk and rarely use feature branches; begin release
> phase by branching, then work towards release in branch, while continuing for
> next iteration in trunk (+currently pom version tag hell, when doing this
> manually+); prepare by tagging from branch, then release from tag
> this could be achieved by offering a new goal release:branch, that creates a
> branch from trunk, updates *the trunk* poms for next iteration and stores
> some properties in the branch, so that upon release:prepare from *the
> branch*, the user can opt out preparations for next iteration on the branch
> - loosely related to following issues:
> -- [branch instead of tag|http://jira.codehaus.org/browse/MRELEASE-179]
> -- [branch during prepare|http://jira.codehaus.org/browse/MRELEASE-170]
--
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
