[jira] [Closed] (MRELEASE-604) release:branch should take the "commitByProject" parameter into account

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-604.
-----------------------------------
    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.

> release:branch should take the "commitByProject" parameter into account
> -----------------------------------------------------------------------
>
>                 Key: MRELEASE-604
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-604
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.0
>         Environment: Maven 2.2.1, Subversion 1.6, Windows, Java 1.6
>            Reporter: Werner Mueller
>            Priority: Major
>
> The release:prepare goal allows to adjust tagging to a flat directory layout by using the 'commitByProject=true' confiuration option: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#commitByProject
> This way the release:perform will add every module into the release tag.
> When using release:branch only the parent module is commited to the created branch. All sub-modules in the flat directory layout are ignored (or end up somewhere else?). The commitByProject option has no effect for branching.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)