Click on the release plugin goals from the page you linked to and the docs describe exactly what it does... for example see: http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html. You'll start appreciating the release plugin when you have a multimodule project with tens of child modules in your hands and the release time comes.
Kalle On Thu, Jul 3, 2008 at 8:59 AM, Peter Horlock <[EMAIL PROTECTED]> wrote: > > > > > > Last point: The release plugin will fail to update the version of your > > current project if it is defined by a property. > > > > Sorry, but what's the purpose of the release plugin anyway? It's site > doesn't really tell it: > http://maven.apache.org/plugins/maven-release-plugin/ > > If I got it right, it should: > 1. Create a tag of the current version of a project > 2. Create a branch of the current version of a project > Did I miss something? > > Hmm. It's not really hard to do this with subversion itself, is it??? > Also, when doing it manually, isn't that better, because you got more > control over what you are really doing? > Same thing with "mvn deploy" - on the one hand, its nice and easy - on the > other hand - isn't it TOO easy to overwrite a > previously deployed version?! > > Don't misinterpret what I am trying to say - I don't want to argue "my way > is better" or so - I just am looking for better > arguments of why I should use it, I am pretty sure it has it value, I just > can't (fully) see it yet. > > Thanks, > > Peter >
