Here is a book excerp :
BetterBuildsWithMaven wrote: > > Try the dry run again: > C:\mvnbook\proficio> mvn release:prepare -DdryRun=true > Now that you've gone through the test run and are happy with the results, > you can go for the real thing > with the following command: > C:\mvnbook\proficio> mvn release:prepare > You'll notice that this time the operations on the SCM are actually > performed, and the updated POM > files are committed. > You won't be prompted for values as you were the first time – since by the > default, the release plugin > will resume a previous attempt by reading the release.properties file that > was created at the end > of the last run. If you need to start from the beginning, you can remove > that file, or run mvn > -Dresume=false release:prepare instead. As I understand, the second prepare call would use configuration values from the previous one. If I do a clean or resume=false, this won't be the case. Just want to say that there is some differences between the book and the plugin. As far as I am concerned a suite mvn release:prepare -DdryRun mvn release:prepare mvn release:perform would be perfect, doing a clean between dryRun and real prepare just waste some time for big projects. Seb -- View this message in context: http://www.nabble.com/Prepare-after-dryRun-does-not-tag-the-scm-tf2310250.html#a6423934 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
