On 24 May 2012, at 4:23 PM, DK wrote: > So how does release work with SVN. > > If all my projects are at <version>1.0.0-SNAPSHOT</version>. > What will running the mvn release command do? > > Will it result in 1.0.1-SNAPSHOT?
Short answer is yes. Long answer: When you ask the release plugin to make a release for you, it performs the following steps for release:prepare: - Checks your code is properly checked in. - Checks your code builds. - Check your tests run. - Bumps the version number from the "snapshot" version 1.0.0-SNAPSHOT to the "release" version 1.0.0 in all affected poms and checks it in. On a multi-module project, this is done on all relevant poms. - Tags your release in SVN. - Bumps the version number from the "release" version 1.0.0 to the next "snapshot" version 1.0.1-SNAPSHOT in all relevant poms and checks it in, ready for further development. You now have a tag. Typically, the next step is to build and deploy your tagged release, which is done with release:perform: - Checks out a pristine fresh copy of the tag. - Builds the tagged code. - Builds the tagged docs. - Runs the tests. - Deploys the built code to the maven repo. - Deploys the built docs to the maven repo. And you're done. If for some reason any part of this process breaks (tests fail, build fails, couldn't contact the server, etc etc), you can roll the entire thing back with release:rollback. Once you've got this working, you will wonder how you put up with doing this manually. Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
