maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (MRELEASE-203) support more than one release pattern via new goal release:branch
Date Sat, 18 Sep 2010 03:45:36 GMT


Brett Porter updated MRELEASE-203:

    Affects Version/s:     (was: 2.1)

> support more than one release pattern via new goal release:branch
> -----------------------------------------------------------------
>                 Key: MRELEASE-203
>                 URL:
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5
>         Environment: irrelevant
>            Reporter: Joerg Buchberger
> 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
> 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 (MRELEASE-179)
> -- branch during prepare (MRELEASE-170)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message