[
https://issues.apache.org/jira/browse/MRELEASE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-869.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Add 'tagByProject' configuration flag to release:prepare
> ---------------------------------------------------------
>
> Key: MRELEASE-869
> URL: https://issues.apache.org/jira/browse/MRELEASE-869
> Project: Maven Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.5
> Environment: Git
> Reporter: codemonkey
> Priority: Major
>
> For projects using Git, it would be convenient for sub projects to be
> referenced as Git submodules. This almost works perfectly in conjunction with
> the 'commitByProject' flag.
> The one additional feature I would want is to have each sub project be
> tagged. A 'tagByProject' flag would have the following semantics:
> * require and/or implicitly set commitByProject=true
> * change the commit message to use the project name rather than the parent
> name
> * tag the commit with a tag based on the project name rather than the parent
> project name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
