Hi, > 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.
It's not so easy, when you change version number of your product there a lot of consequences (bugzilla, scripts, external communication ...). So I may chose the second solution :) Thanks. On Friday 02 March 2007 18:22, Thierry Lach wrote: > I suppose that depends on who's best practices they are, which best > practices they are, and how important they are. I'd really hate to put an > issue like the format of a release number on the same par as doing a > release without running the tests. > > Quite frankly, the "version starting with a letter" approach may possibly > be superior to the current Maven approach (I don't know if it is, but it > might be) . > > If Maven is going to continue to be accepted by businesses that will allow > open-source software, there is going to have to be some flexibility. > > On 3/2/07, Wayne Fay <[EMAIL PROTECTED]> 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]
