release:rollback does not honor -DcommitByProject -------------------------------------------------
Key: MRELEASE-616 URL: http://jira.codehaus.org/browse/MRELEASE-616 Project: Maven 2.x Release Plugin Issue Type: Bug Components: rollback Affects Versions: 2.1 Reporter: Steven Schlansker 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira