Comments on: The Maven Release Plugin Is Pretty Slick

By: Alexandre

Alexandre — Thu, 09 Apr 2009 22:55:09 +0000

I have a problem with maven release with mercurial.
It works well if your pom.xml is at the root of your repo but I did not succeed to work if there are modules and want release modules seperately.
The problem comes from (I think) the hg clone does not manage subdirectories (as you can do on cvs or svn).
Someone has a solution?

By: Jason Lee

Jason Lee — Fri, 03 Apr 2009 17:17:46 +0000

Brett and Olivier, Thanks for the tip. Someone on twitter actually pointed me in the direction of 2.1.0′s new feature minutes after I posted this. I think I have everything set up correctly for that now, so I’ll be able to test it when next I need to do a release, which should be soon. The CLI option isn’t real appealing as the password is then stored in my shell’s history file.

By: Olivier Lamy

Olivier Lamy — Fri, 03 Apr 2009 07:19:32 +0000

Nice to see someone happy about maven stuff .
If you don’t want to store scm username/password use the following parameters in your cli : -Dusername= -Dpassword=

By: Brett Porter

Brett Porter — Fri, 03 Apr 2009 06:15:07 +0000

glad you like it!

if you’re concerned about cleartext passwords, Maven 2.1.0 allows you to encrypt them (though that won’t help with the plugin that foolishly spits it out in the build process!)

By: Jason Lee

Jason Lee — Fri, 03 Apr 2009 03:35:47 +0000

Hi, Bruce. Thanks for the tips. I have a LOT to learn still about Maven, but I’m committed. It’s a great tool that gets better the more you learn it.

By: Bruce Snyder

Bruce Snyder — Fri, 03 Apr 2009 03:32:04 +0000

A very cool feature of the release:prepare goal is that the release.properties file that is generated can be committed to SCM. This allows a given release to be completely and easily recreated at any time. Also, don’t forget about the dryRun property that prevents checkin or tagging to allow for a practice run so that the project is left untouched.

Also, with large projects, Maven’s batch mode option (mvn -B) can be very useful so that Maven won’t ask those questions for every module that is being deployed (think about deploying 20, 40 or more modules at once).