Wendy Smoak wrote:
On 11/22/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
The main point here is that one would like to have -exactly- -one- place
where version numbers are defined and changed. Forcing people to
manually edit dozens of pom.xml files every time the version number
changes is just bad design.
The intent is for you to use the release plugin, and for Maven to
update these version numbers during the release process.
http://maven.apache.org/plugins/maven-release-plugin/introduction.html
Trouble with that is that it assumes that our release process maps to
the assumptions made in the plugin. I actually don't have too much of a
beef with it, but it does not address some of the issues that arise in
the non-java world, and it requires that you keep state externally.
I guess my one line criticism is that the release plugin assumes you
know ahead of time that you are going to release this exact upcoming build.
Granted, I'm still a maven newbie and I accept the fact that I may
understand all of the design decisions - so be patient with me please :)
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
