Indeed, Indeed there are few projects that use a letter to start the version number, but it's not my choice and I can't change that (immediatly). But it's true that like Daniel said, even with a maven-style versionning convention there are some cases where it could be a good thing to be able to specify the next version to use for starting the new version of the project.
Regards, Elid. On Monday 05 March 2007 16:49, Daniel Kulp wrote: > Wayne, > > There are several cases where the --batch-mode auto stuff of maven doesn't > work in quite a "desirable" way so the aforementioned flag would be > GREATLY appreciated. > > Examples: > > 1) 1.0-SNAPSHOT would be auto set to 1.1-SNAPSHOT, but many times we'd like > it to go to 1.0.1-SNAPSHOT > > 2) 2.0-incubating-RC1-SNAPSHOT seems to autoset to 2.1-something.... > > There are others. For our internal projects, we've written some perl > scripts to 'cleanup' the pom versions once the release plugin is done > mangling them. Would be nice not to have to do that. > > Dan > > On Friday 02 March 2007 11:18, Wayne Fay wrote: > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
