[MRELEASE-616] release:rollback does not honor -DcommitByProject

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3.2
• Component/s: rollback
• Assignee: Robert Scholte
• Reporter: Steven Schlansker
• Created: 17/Nov/10 13:03
• Updated: 04/Jun/12 12:42
• Resolved: 02/Jun/12 06:27

Description

MRELEASE-168 added a commitByProject flag to release:prepare for situations where you have a project layout

proj/
mod1/
mod2/

where proj, mod1, mod2 are all different SCM repositories.
Effectively, instead of doing

commit proj/pom.xml proj/mod1/pom.xml proj/mod2/pom.xml

it will run

commit proj/pom.xml
commit proj/mod1/pom.xml
commit proj/mod2/pom.xml

This works great, but release:rollback doesn't know about this and still tries to commit them all in one go, which fails if they are different source repositories.