Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKoNANuLKhnDdmEbhsYAvFyCk8rTzADEBb2gadiF0+Mx8VH_5w@mail.gmail.com>
References: 
 <CAKoNANuLKhnDdmEbhsYAvFyCk8rTzADEBb2gadiF0+Mx8VH_5w@mail.gmail.com>
Date: Thu, 7 Apr 2016 09:27:00 +0200
Message-ID: 
 <CAKE+Mjp=rVfbFq27qHaCBsd05N4fK-eXZM38XwBDQgbEsS7FHA@mail.gmail.com>
Subject: Re: Usage of SNAPSHOT qualifier in package exports
From: Julian Sedding <jsedding@gmail.com>
To: dev@felix.apache.org
Cc: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ra=C3=BAl

A simple workaround to remove this ambiguity is to use odd micro
versions for snapshots only and even micro versions for releases. We
use this strategy in the Apache Sling project successfully since
several years.

I.e.
1.0.1-SNAPSHOT
1.0.2 <-- release
1.0.3-SNAPSHOT
1.0.4 <-- release

Regards
Julian

On Wed, Apr 6, 2016 at 5:36 PM, Raul Kripalani <raulk@apache.org> wrote:
> During a discussion in the Camel dev@ list about possibly adopting the
> bnd-maven-plugin, a contributor noticed differences in the way that packa=
ge
> export versions are computed between Felix' maven-bundle-plugin and the
> former.
>
> http://camel.465427.n5.nabble.com/DISCUSS-Moving-from-maven-bundle-plugin=
-to-bnd-maven-plugin-and-SNAPSHOT-versions-tp5780520.html
>
> * maven-bundle-plugin transforms the -SNAPSHOT qualifier to .SNAPSHOT.
> * bnd-maven-plugin transforms the -SNAPSHOT qualifier to .<timestamp>.
>
> OSGi sorts versions in alphanumeric order, which means that, to the eyes =
of
> an OSGi container, 1.0.0.SNAPSHOT is higher than 1.0.0 (!).
>
> https://versionatorr.appspot.com/?a=3D1.0.0-SNAPSHOT&b=3D1.0.0
>
> Sure this is a minor issue, with practically zero impact. I can't think o=
f
> a use case where one would deploy the same bundle twice in production, as=
 a
> SNAPSHOT and as final.
>
> It seems that your artefacts are affected, based on the MANIFEST.MF in th=
is
> bundle as an example:
> https://repository.apache.org/content/groups/snapshots/org/apache/felix/o=
rg.apache.felix.fileinstall/3.5.3-SNAPSHOT/org.apache.felix.fileinstall-3.5=
.3-20160401.145250-1.jar
> .
>
> As I said, not a biggie, but being Felix a leader in the OSGi technology
> space, I would like to hear your thoughts, as it's a matter of semantic
> correctness and adherence to the OSGi principles.
>
> Cheers,
>
> *Ra=C3=BAl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> Blog: raul.io
> <http://raul.io/?utm_source=3Demail&utm_medium=3Demail&utm_campaign=3Dapa=
che> |
> twitter: @raulvk <https://twitter.com/raulvk>