On Mon, Feb 7, 2011 at 09:14, Christian Schneider <[email protected]> wrote: > Hi Guillaume, > > I know that in Camel we use 2.2.0.qualifier for this. As far as I know > ".qualifier" is the notion in osgi for snapshot. > Perhaps this could help. The only problem is that there is no automatic > conversion in the bundle plugin. So I think there is an > ant script in the camel build that creates the version. So the way you go > with the .99 notation is perhaps easier.
The bundle plugin has a goal to convert maven versions to osgi versions since 2.1.0 afaik. The camel poms should be updated to leverage it. > > Christian > > > Am 07.02.2011 09:06, schrieb Guillaume Nodet: >> >> Right, the reason is the OSGi versioning. >> In OSGi, 2.2-SNAPSHOT> 2.2.0, so it can cause artifacts to be badly >> wired against the snapshot instead of the release. So you can't >> really deploy snapshots and releases at the same time. >> On the other hand, it you build an artifact that import >> 2.1.99-SNAPSHOT and you need a range of up to the next minor version, >> it doesn't work either because the range has to be [2.1,2.2) or >> [2.1,2.3) which will have to be changed anyway when 2.2 is released so >> that it becomes [2.2,2.3). >> Given there are drawbacks in both, I'd have no problem to change if >> people think it's less confusing. The first problem may actually be >> less important than the second one. >> >> In all cases, we should be consistent. >> >> On Mon, Feb 7, 2011 at 08:47, Andreas Pieber<[email protected]> wrote: >>> >>> Hey christian, >>> >>> I'm also not sure for 100% but I think it has something to do with osgi >>> versioning (that's also the reason y felix always jumps one version); but >>> Guillaume can explain in detail :) >>> >>> kind regards, >>> andreas >>> >>> On Mon, Feb 07, 2011 at 08:30:43AM +0100, Christian Schneider wrote: >>>> >>>> Why not simply use : >>>> >>>> For a stable branch: >>>> 2.1.4-SNAPSHOT -> 2.1.4 -> 2.1.5-SNAPSHOT -> 2.1.5 >>>> >>>> For the develop branch: >>>> 2.2-SNAPSHOT -> 2.2.0 -> 2.3-SNAPSHOT -> 2.3.0 >>>> >>>> I think most projects use this scheme. >>>> >>>> Christian >>>> >>>> >>>> Am 07.02.2011 08:09, schrieb Andreas Pieber: >>>>> >>>>> Hey, >>>>> >>>>> We've decided some time ago now to step from one version to the other >>>>> and not >>>>> jumping releases in between like felix does. Therefore we use quite >>>>> "strange" >>>>> snapshot versions (e.g. 2.99.99-SNAPSHOT for 3.0.0 or 2.1.99-SNAPSHOT >>>>> for >>>>> 2.2.0). But on the 2.1.x branch we use 2.1.4-SNPASHOT for 2.1.4. Well, >>>>> I think >>>>> something is wrong here :) >>>>> >>>>> IMHO we can either use 2.1.3.99-SNAPSHOT for 2.1.4 or simply switch >>>>> back at >>>>> 2.0.99-SNAPSHOT after releasing; in other words we have two options: >>>>> >>>>> 2.1.3.99-SNAP -> 2.1.4 -> 2.1.4.99-SNAP -> 2.1.5 >>>>> 2.0.99-SNAP -> 2.1.4 -> 2.0.99-SNAP -> 2.1.5 >>>>> >>>>> I slightly prefer the first method since it maps the versions we choose >>>>> for all >>>>> other snapshots but basically I'm indifferent :) >>>>> >>>>> WDYT? >>>>> >>>>> kind regards, >>>>> andreas >>>>> >>>> -- >>>> ---- >>>> http://www.liquid-reality.de >>>> >> >> > > -- > ---- > http://www.liquid-reality.de > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
