[MRELEASE-745] Property suppressCommitBeforeBranch also suppresses trunk commit AFTER branching.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Component/s: branch
• Environment: Windows (7, Server 2003), Maven 2.2.1, Jenkins 1.420
• Assignee: Robert Scholte
• Reporter: Chris Wilton
• Created: 05/Mar/12 08:26
• Updated: 15/Apr/12 14:01
• Resolved: 15/Apr/12 14:01

Description

I have a multi-module maven project. I create 'release branches' for testing, then once testing is complete, I create the release tag from the branch.

In order to work around the subversion 1.5.x problem (http://jira.codehaus.org/browse/SCM-515) I have the following properties set:
suppressCommitBeforeBranch=true
suppressCommitBeforeTag=true
remoteTagging=false

Implicit (as default) values are:
updateBranchVersions=false
updateWorkingCopyVersions=true

The intention is to create a branch with the same pom versions as the trunk, without committing any modifications to the trunk (in order to avoid the SCM section for the branch ending up in the trunk poms), then to bump up the trunk versions and commit them. But although the trunk pom versions are modified, they are not committed.

I want commit suppressed BEFORE branching, not AFTER, else I have to run release:update-versions afterwards and perform a manual commit, to bump up the trunk versions. I should mention that this is being run as a (parameterized) Jenkins task, so it is not simply a case of manually committing my working copy to the trunk after the branching process is complete.

Am I doing something wrong?