A question about version numbering in Subversion. I am aware of the way subversion handles version information while releasing. As I have peeked overhere in the Maven repository:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin-2.0-beta-4/src/main/java/org/apache/maven/plugins/release/versions/DefaultVersionInfo.java Now I am wondering about something. My current contract would like a build increment value in between two brackets. Which auto increases with each build delivered to production. I'd say that hooking into the deploy phase would be a good time for such actions. But then I figure that it isn't. I'd say the initialize phase is the correct one. Since I am not processing resources or sources but the POM.xml. The thing is this, can I modify the POM then and there and keep the build going or do I need to modify the POM. And let the user start another run, just like the release plugin does? Also, is it possible (by documented API or acceptable convention) to detect whether or not a build is running up to or past the deploy phase? The thing is that I don't want to generate "new" builds during development, overwriting the current snapshot is preferred. But when processing a project which will be "publicly" available, I want to be able to identify it (even a snapshot) with an incremented build number, but without having to manage the version setting by hand. Any suggestions are greatly apreciated. Kind regards, Jeroen Leenarts http://blog.leenarts.net Download this as a file --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
