1.2.3.5-SNAPSHOT I don't think we'd be needing SNAPSHOT here All is needed from the user of the parent pom's point of view is the 1.2.3 since in terms of functionality and testability nothing's changed.. So other poms that has dependencymanagement pointing at 1.2.3 doesn't need to know about the fact that it's at build 4 or 5.
But if a new test case is introduced then the maintainer of the 1.2.3.4 pom should increment the bug-fix number (or whatever name is best used here) so the new version would be 1.2.4.0 While saying that the pom itself must know at what version it is in..1.2.3.5 or 1.2.4.0 Is my point clearer? johan > -----Original Message----- > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 19, 2007 2:17 PM > To: [EMAIL PROTECTED] > Subject: Re: Maven2 release process in Continuum > > what aspect of maven do you think is killing this use case? > > 1.2.3.4-SNAPSHOT when its run through the release process will offer > up as a default 1.2.3.5-SNAPSHOT as the new development version and > 1.2.3.4 as the released version... > > deployment will work...whats killing this for you? > > and the release process will let you change that if it doesn't guess > right... > > jesse > > On 7/19/07, Johan Iskandar <[EMAIL PROTECTED]> wrote: > > > > > > > From: Jesse McConnell [mailto:[EMAIL PROTECTED] > > > > > > ok, I am a bit confused by what your actually asking here... > > > > > > but there is no reason in the world you can't use w.x.y.z > > versioning... > > > > > Well, since maven's main idea is to promote conventions.. and these > > conventions is there to ease and straighten out development process, why > > not take it to this level of detail..? > > It would ease versioning path details out of the developers mind.. > > > > Best regards, > > Johan > > > > > > > -- > jesse mcconnell > [EMAIL PROTECTED]
