Yep I'm seeing the same behavior Martin, which is different in Maven 2.2.1 which properly using the mvn release:prepare and mvn release:perform steps:
1. Replaced version #s in the trunk with Version N+1-SNAPSHOT 2. Created the tag with the un-SNAPSHOT versioned elements (e.g., 0.3) I'm also seeing the same behavior now in Apache OODT as I try and release version 0.6. So, there is something up in the new Maven 3 version that I am for the first time using in both of these instances to perform the release. I was going to go ahead and blow away the 0.3 tag in SIS, after performing some more experiments. I'm wondering if some properties in the <scm> section of our poms are incorrect (also in OODT) that Maven 2.2.1 would happily ignore, but that Maven 3 is not happy about especially during the mvn release stages. So if you can shed some light into the above, thanks and great. Otherwise, I'm also investigating it. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Monday, July 8, 2013 9:04 AM To: Apache SIS <[email protected]> Subject: Release experiment >I'm not very familiar with the "mvn release" plugins, but maybe it is >designed for a context slightly different than our current one? (unless >I missed some configuration parameters). I though that we could create >the 0.3 branch before to release, since some material are removed on >that branch compared to the trunk. But the plugins replaced the >0.3-SNAPSHOT version numbers by 0.4-SNAPSHOT on the branch, leaving >trunk unchanged. Strangely, it created a 0.3 tags which still have the >0.3-SNAPSHOT version number instead than a plain 0.3. Maybe we have done >something wrong? > >I wonder, given that there is some additional steps to do (e.g. replace >the "0.3-SNAPSHOT" string in some Java constants too), we may have to >customize the release process anyway. Does anyone have some experience >about customizing the Maven release process? Or what about exploring the >opportunity of creating a Ant task? > >My understanding is that "mvn release" just performs version number >change and commit a tag on the SVN. Signing the JAR files is done by the >Maven "package" phase, which would still be executed. Is that right? > > Martin >
