On Fri, Oct 15, 2010 at 3:50 AM, Antonio Petrelli <[email protected]> wrote: > 2010/10/15 Phillip Hellewell <[email protected]>: >> 1. Change version in pom; check it in, tag it, change version back; check it >> in. > > This is exactly how release plugin behaves.
So I just read over release:prepare and I noticed it mentions that it will prompt you for a lot of things. Is there any way to automate this so it will be non-interactive short of writing my own plugin? I want it to create the tag automatically using the version number as the name. I want it to update the version number automatically by incrementing the last number by one. In other words, I want it to: 1. Perform basic checks (no changes to source, no snapshot dependencies). 2. Change x.y.z.w-SNAPSHOT to x.y.z.w in the pom. 3. (compile,install,deploy) 4. Commit updated pom. 5. Create tag, named automatically after the version number. 6. Change x.y.z.w to x.y.z.(w+1)-SNAPSHOT in the pom. 7. Commit updated pom. I want to integrate this with our Hudson builds, and I want to make it so basically w == the Hudson build number. (Any changes to x, y, or z will be done manually as we create branches.) Thanks, Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
