You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2009/07/30 18:15:12 UTC
Re: svn commit: r799305 - in /synapse/branches/1.3: ./
modules/commons/
modules/core/ modules/distribution/ modules/experimental/
modules/extensions/
modules/handler/ modules/packaging/package-archetype/
modules/packaging/package-archetype/src/main/r
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
> <andreas.veithen@gmail.com <ma...@gmail.com>> wrote:
>
> Why not 1.3.1-SNAPSHOT??
>
> Andreas
>
> On Thu, Jul 30, 2009 at 18:00, Ruwan Linton<ruwan.linton@gmail.com
> <ma...@gmail.com>> 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
> <ruwan.linton@gmail.com <ma...@gmail.com>>
> > 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
> <ruwan.linton@gmail.com <ma...@gmail.com>>
> >> wrote:
> >>>
> >>>
> >>> On Thu, Jul 30, 2009 at 8:44 PM, Glen Daniels
> <glen@thoughtcraft.com <ma...@thoughtcraft.com>>
> >>> wrote:
> >>>>
> >>>> Hi Ruwan:
> >>>>
> >>>> ruwan@apache.org <ma...@apache.org> 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: dev-unsubscribe@synapse.apache.org
> <ma...@synapse.apache.org>
> >>>> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Ruwan Linton
> >>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >>> WSO2 Inc.; http://wso2.org
> >>> email: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: svn commit: r799305 - in /synapse/branches/1.3: ./
modules/commons/ modules/core/ modules/distribution/ modules/experimental/
modules/extensions/ modules/handler/ modules/packaging/package-archetype/
modules/packaging/package-archetype/src/main/r
Posted by Andreas Veithen <an...@gmail.com>.
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<ru...@gmail.com> 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 <gl...@thoughtcraft.com> 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
>> > <andreas.veithen@gmail.com <ma...@gmail.com>> wrote:
>> >
>> > Why not 1.3.1-SNAPSHOT??
>> >
>> > Andreas
>> >
>> > On Thu, Jul 30, 2009 at 18:00, Ruwan Linton<ruwan.linton@gmail.com
>> > <ma...@gmail.com>> 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
>> > <ruwan.linton@gmail.com <ma...@gmail.com>>
>> > > 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
>> > <ruwan.linton@gmail.com <ma...@gmail.com>>
>> > >> wrote:
>> > >>>
>> > >>>
>> > >>> On Thu, Jul 30, 2009 at 8:44 PM, Glen Daniels
>> > <glen@thoughtcraft.com <ma...@thoughtcraft.com>>
>> > >>> wrote:
>> > >>>>
>> > >>>> Hi Ruwan:
>> > >>>>
>> > >>>> ruwan@apache.org <ma...@apache.org> 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: dev-unsubscribe@synapse.apache.org
>> > <ma...@synapse.apache.org>
>> > >>>> For additional commands, e-mail: dev-help@synapse.apache.org
>> > <ma...@synapse.apache.org>
>> > >>>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> Ruwan Linton
>> > >>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> > >>> WSO2 Inc.; http://wso2.org
>> > >>> email: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341
>> > 3097
>> > > blog: http://ruwansblog.blogspot.com
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> > <ma...@synapse.apache.org>
>> > For additional commands, e-mail: dev-help@synapse.apache.org
>> > <ma...@synapse.apache.org>
>> >
>> >
>> >
>> >
>> > --
>> > Ruwan Linton
>> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> > WSO2 Inc.; http://wso2.org
>> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
>> > blog: http://ruwansblog.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: svn commit: r799305 - in /synapse/branches/1.3: ./
modules/commons/ modules/core/ modules/distribution/ modules/experimental/
modules/extensions/ modules/handler/ modules/packaging/package-archetype/
modules/packaging/package-archetype/src/main/r
Posted by Ruwan Linton <ru...@gmail.com>.
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 <gl...@thoughtcraft.com> 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
> > <andreas.veithen@gmail.com <ma...@gmail.com>> wrote:
> >
> > Why not 1.3.1-SNAPSHOT??
> >
> > Andreas
> >
> > On Thu, Jul 30, 2009 at 18:00, Ruwan Linton<ruwan.linton@gmail.com
> > <ma...@gmail.com>> 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
> > <ruwan.linton@gmail.com <ma...@gmail.com>>
> > > 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
> > <ruwan.linton@gmail.com <ma...@gmail.com>>
> > >> wrote:
> > >>>
> > >>>
> > >>> On Thu, Jul 30, 2009 at 8:44 PM, Glen Daniels
> > <glen@thoughtcraft.com <ma...@thoughtcraft.com>>
> > >>> wrote:
> > >>>>
> > >>>> Hi Ruwan:
> > >>>>
> > >>>> ruwan@apache.org <ma...@apache.org> 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: dev-unsubscribe@synapse.apache.org
> > <ma...@synapse.apache.org>
> > >>>> For additional commands, e-mail: dev-help@synapse.apache.org
> > <ma...@synapse.apache.org>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Ruwan Linton
> > >>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > >>> WSO2 Inc.; http://wso2.org
> > >>> email: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; 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: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341
> 3097
> > > blog: http://ruwansblog.blogspot.com
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > <ma...@synapse.apache.org>
> > For additional commands, e-mail: dev-help@synapse.apache.org
> > <ma...@synapse.apache.org>
> >
> >
> >
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com