You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ralph Goers (JIRA)" <ji...@codehaus.org> on 2015/02/07 06:38:18 UTC
[jira] (MRELEASE-604) release:branch should take the
"commitByProject" parameter into account
[ https://jira.codehaus.org/browse/MRELEASE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers reopened MRELEASE-604:
----------------------------------
This still seems to be a valid issue and I am experiencing the same problem.
> release:branch should take the "commitByProject" parameter into account
> -----------------------------------------------------------------------
>
> Key: MRELEASE-604
> URL: https://jira.codehaus.org/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
>
> 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
(v6.1.6#6162)