Thanks for the answers. This would all be fine if maven were the primary build mechanism for ManifoldCF, but it is not at this time, for many reasons. From your description the pom's should remain -SNAPSHOT in the release if this is the case, no? Also, is there any way to have it not change anything other than the pom's themselves? I don't want maven to create svn tags etc.
Karl On Thu, Sep 8, 2011 at 2:58 AM, Tommaso Teofili <tommaso.teof...@gmail.com> wrote: > Nope, using the maven-release-plugin [1] would be enough as it takes care of > checking/changing versions both in the dependencies (if there is any > -SNAPSHOT dependency) and in the modules' versions. > A very quickly look at the process goes like running mvn release:prepare > which signs artifact, creating a svn tag with the release version and > preparing the poms for the next development version, then if the RC is ok > run mvn release:perform otherwise if there is any problem run mvn > release:rollback to bring back the trunk to the -SNAPSHOT version. > One more nice thing would be to add the apache-pom as parent pom of our > manifoldcf-parent: > > <parent> > <groupId>org.apache</groupId> > <artifactId>apache</artifactId> > <version>9</version> > <relativePath /> > </parent> > > this will allow using the -Papache-release option (enabling the > apache-release profile) to create reports and sign artifacts. > Hope this helps. > Tommaso > > 2011/9/8 Karl Wright <daddy...@gmail.com> > >> Hi folks, >> >> I'm handling the 0.3-incubating release of MCF, and I'm trying to >> figure out what the <version> tags in the maven pom files should say. >> They currently say 0.3-SNAPSHOT. Should I edit them in the release >> branch to be just 0.3? >> >> Karl >> >
