I don't know if I entirely agree with that. Maven is not just a tool to help you compile and build your Java projects -- it also "gently" enforces a collection of best practices for building Java projects. It seems like your "version starting with a letter" does not meet Maven's concept of "best practice in version naming", and so you're running into some troubles.
In all likelihood, if that feature does not exist it is simply because no one has asked for it or the priority for the feature was low enough that it simply wasn't done yet. Personally, I would be pragmatic about this and just adopt the Maven-style versioning so that release would work properly. Or you could hack the release plugin code, add this functionality, and contribute it back via JIRA as an enhancement. Wayne On 3/2/07, Thierry Lach <[EMAIL PROTECTED]> wrote:
If it doesn't, it should. On 3/2/07, Elid OR <[EMAIL PROTECTED]> wrote: > > Hi all, > > Here my problem, I would like to specify the next version of my project > when I > release with the maven 2 release plugin in batch mode (in a continuous > integration process) because it does not handle my incrementation > convention. > In fact It can not parse the version number for incrementing because it > starts with a letter. > > Is there a way to specify the next version number of a release when using > batch mode ? Something like "mvn > release:prepare -Dmaven.next.version=my.next.version --batch-mode" ? > > I did not find anything in the documentation. > > Thanks > > Elid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
