[OODT-643] Maven Release Plugin generates incorrect tag and trunk version numbers

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 0.6
• Fix Version/s: 0.8.1
• Component/s: build proces

Environment

Java6
Mac OS X 10.8.2
Maven3

• Skill Level: Newcomer (Easy) - Everyone can do this
• Assignee: Tom Barber
• Reporter: Chris A. Mattmann
• Created: 08/Jul/13 17:22
• Updated: 29/Jan/15 06:40
• Resolved: 30/Dec/14 23:57

Description

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:

[terra:~/src/oodt/trunk] mattmann% grep -R "0.6-SNAPSHOT" * | grep pom.xml | grep -v "text-base" | grep -v "target"
cli/pom.xml:		<version>0.6-SNAPSHOT</version>
commons/pom.xml:    <version>0.6-SNAPSHOT</version>
core/pom.xml:    <version>0.6-SNAPSHOT</version>
metadata/pom.xml:    <version>0.6-SNAPSHOT</version>
pcs/input/pom.xml:    <version>0.6-SNAPSHOT</version>
protocol/api/pom.xml:		<version>0.6-SNAPSHOT</version>
protocol/ftp/pom.xml:		<version>0.6-SNAPSHOT</version>
protocol/http/pom.xml:		<version>0.6-SNAPSHOT</version>
protocol/imaps/pom.xml:		<version>0.6-SNAPSHOT</version>
[terra:~/src/oodt/trunk] mattmann%