On 3/8/07, Erik Drolshammer <[EMAIL PROTECTED]> wrote:
<snip> _Questions_:
a. Is this the procedure you want?
b. Is this procedure supported by the release-plugin?
c. Is this best practice? If not, what's wrong or should be changed?
The release plugin will create the tag/branch for you. The pom.xml in the tag will have the version at x.y. The plugin will then change the pom.xmlon the trunk to have version x.y+1-SNAPSHOT. Which is great. It handles all of the -SNAPSHOT references you may have in other sub projects. The process I'm trying to understand is post-release. It is easy to continue to develop on the trunk and then run the release plugin again, but how do we do development on the branch and then use the release plugin. It would seem we need to manually update the version numbers in the poms. Once that is done, the release plugin can do it's job again. I'm looking to see if someone has a repeatable process for doing this with the help of maven tools. Maven may not cover everything in our process, but, if it can do something, I want to use it. Neil
