During the release:prepare and release:perform step of the 0.6 release, I ran into some real weirdness. Mainly:
- some modules were processed in trunk as still having the 0.6-SNAPSHOT version number (see below)
- the 0.6 tag generated these same modules as having version 0.6-SNAPSHOT
I had to modify the above by hand to get it working. I also had to fake and update the pom.xml (root pom) to 0.7-SNAPSHOT to get it building after the mvn release:prepare step (and before mvn release:perform).
This coupled with the random test failures in the protocol-* plugins, as well as initially in commons and then later randomly in workflow and other places, made building the RC a nightmare. We'll need to fix these for the 0.7 release.
Here's the list of poms that didn't get transformed properly: