Affects Version/s: None
Fix Version/s: 1.6
Environment:m11b3, scm plugin
Number of attachments :
MRELEASE-77 for the equivalent m2 problem.
Currently, the scm:prepare-release goal modifies the files project.xml and changes.xml, then commits the changes and tags the entire source tree, all in one step. If there is a problem with updating the files, we have a faulty version checked in and tagged in the repository. And usually, there are problems (see
MPSCM-1, MPSCM-12, MPSCM-43, MPSCM-67, ...?).
Given this immature state of the plugin, I think it is necessary that we provide the possibility to undo any unwanted modifications before anything gets checked in and tagged. I'm just not sure about the best way to do that:
- move the check-in and tagging into the scm:perform-release goal, so prepare release only updates project.xml and changes.xml
- add a new goal for updating project.xml and changes.xml
- add a property 'testmode' like in m2, that skips the check-in and tagging (not sure how that would help when there are problems though)
I'd prefer the second choice, what do others think?