Actually, it's not just a convention. We have no other choice because Maven would consider 0.0.0-SNAPSHOT as older than e.g. 1.2 and this would break the version management in Maven.
Andreas On Thu, Jul 30, 2009 at 18:31, Ruwan Linton<[email protected]> wrote: > Glen, > > Hhhmmm, that's logical and I didn't knew this convention. > > +1 for 1.4.0-SNAPSHOT as the trunk version, which can be modified as > appropriate after branching out for the next release. > > Thanks, > Ruwan > > On Thu, Jul 30, 2009 at 9:45 PM, Glen Daniels <[email protected]> wrote: >> >> I think one popular pattern (the one the release plugin supports by >> default, >> for instance) is for the trunk to reflect the next version expected to be >> released *from the trunk*. So after 1.3, for instance, the trunk might >> change to "1.4-SNAPSHOT", where further 1.3 development (including point >> releases like 1.3.1) would continue on the 1.3 branch. >> >> Thoughts on that? >> >> --Glen >> >> Ruwan Linton wrote: >> > Fine with me... but that sounds like a branch version but not really the >> > trunk version. >> > >> > Thanks, >> > Ruwan >> > >> > On Thu, Jul 30, 2009 at 9:32 PM, Andreas Veithen >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > Why not 1.3.1-SNAPSHOT?? >> > >> > Andreas >> > >> > On Thu, Jul 30, 2009 at 18:00, Ruwan Linton<[email protected] >> > <mailto:[email protected]>> wrote: >> > > Done! >> > > >> > > BTW: What do you guys think about the trunk version scheme that I >> > proposed >> > > (0.0.0-SNAPSHOT) >> > > >> > > Thanks, >> > > Ruwan >> > > >> > > On Thu, Jul 30, 2009 at 9:25 PM, Ruwan Linton >> > <[email protected] <mailto:[email protected]>> >> > > wrote: >> > >> >> > >> Andreas/Glen, >> > >> >> > >> Yeah, I just tested it and it seems like the maven bundle plugin >> > takes >> > >> care of the conversion from '-' to '.' >> > >> >> > >> Will change the version as appropriate. >> > >> >> > >> Thanks, >> > >> Ruwan >> > >> >> > >> On Thu, Jul 30, 2009 at 9:21 PM, Ruwan Linton >> > <[email protected] <mailto:[email protected]>> >> > >> wrote: >> > >>> >> > >>> >> > >>> On Thu, Jul 30, 2009 at 8:44 PM, Glen Daniels >> > <[email protected] <mailto:[email protected]>> >> > >>> wrote: >> > >>>> >> > >>>> Hi Ruwan: >> > >>>> >> > >>>> [email protected] <mailto:[email protected]> wrote: >> > >>>> > --- synapse/branches/1.3/modules/commons/pom.xml (original) >> > >>>> > +++ synapse/branches/1.3/modules/commons/pom.xml Thu Jul 30 >> > 15:00:45 >> > >>>> > 2009 >> > >>>> > @@ -26,7 +26,7 @@ >> > >>>> > <parent> >> > >>>> > <groupId>org.apache.synapse</groupId> >> > >>>> > <artifactId>Apache-Synapse</artifactId> >> > >>>> > - <version>SNAPSHOT</version> >> > >>>> > + <version>1.3.0.SNAPSHOT</version> >> > >>>> >> > >>>> Isn't the canonical Maven pattern 1.3.0-SNAPSHOT (i.e. >> > "SNAPSHOT" as the >> > >>>> version qualifier)? [1] >> > >>> >> > >>> Glen, the issue is that OSGi containers expect the bundle >> > version scheme >> > >>> to be major.minor.micro.qualifier where as if we put in the '-' >> > to separate >> > >>> the qualifier we will need to have a different value as the >> > bundle version >> > >>> (which is going to go into the MANIFEST). >> > >>> >> > >>> Managing the versions this way will make it consistent with the >> > OSGi >> > >>> versioning scheme, while it is OK with maven. >> > >>> >> > >>> Thanks, >> > >>> Ruwan >> > >>> >> > >>>> >> > >>>> --Glen >> > >>>> >> > >>>> [1] >> > >>>> >> > >>>> >> > >> > http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html >> > >>>> >> > >>>> >> > >> > --------------------------------------------------------------------- >> > >>>> To unsubscribe, e-mail: [email protected] >> > <mailto:[email protected]> >> > >>>> For additional commands, e-mail: [email protected] >> > <mailto:[email protected]> >> > >>>> >> > >>> >> > >>> >> > >>> >> > >>> -- >> > >>> Ruwan Linton >> > >>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> > >>> WSO2 Inc.; http://wso2.org >> > >>> email: [email protected] <mailto:[email protected]>; cell: +94 77 341 >> > 3097 >> > >>> blog: http://ruwansblog.blogspot.com >> > >> >> > >> >> > >> >> > >> -- >> > >> Ruwan Linton >> > >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> > >> WSO2 Inc.; http://wso2.org >> > >> email: [email protected] <mailto:[email protected]>; cell: +94 77 341 >> > 3097 >> > >> blog: http://ruwansblog.blogspot.com >> > > >> > > >> > > >> > > -- >> > > Ruwan Linton >> > > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> > > WSO2 Inc.; http://wso2.org >> > > email: [email protected] <mailto:[email protected]>; cell: +94 77 341 >> > 3097 >> > > blog: http://ruwansblog.blogspot.com >> > > >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > <mailto:[email protected]> >> > For additional commands, e-mail: [email protected] >> > <mailto:[email protected]> >> > >> > >> > >> > >> > -- >> > Ruwan Linton >> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> > WSO2 Inc.; http://wso2.org >> > email: [email protected] <mailto:[email protected]>; cell: +94 77 341 3097 >> > blog: http://ruwansblog.blogspot.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: [email protected]; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
