camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <ra...@apache.org>
Subject Re: [DISCUSS] - Moving from maven-bundle-plugin to bnd-maven-plugin and SNAPSHOT versions
Date Wed, 06 Apr 2016 15:18:55 GMT
On Wed, Apr 6, 2016 at 12:29 AM, David Jencks <
david_jencks@yahoo.com.invalid> wrote:

> I don’t know how camel is doing release versions after a period of
> development, but recall that osgi version 1.2.3.SNAPSHOT is after 1.2.3, so
> if you use normal maven release practices and version the exported packages
> the same as the bundle version (a terrible idea, but IIUC what you are
> doing), then a snapshot would be preferred over a release version as it
> appears to be later.


David, that's a very good point. Evidence here:
https://versionatorr.appspot.com/?a=2.18-SNAPSHOT&b=2.18.
Substituting SNAPSHOT by the timestamp doesn't help either (like
bnd-maven-plugin does), because OSGi would still consider that version
higher than one without the timestamp (2.18.0.201504041000 > 2.18.0).

My opinion is that Camel should follow the methodology that OSGI expert
communities @ the ASF use: Felix and Karaf.

What I'm seeing is that Felix does use the SNAPSHOT qualifier in their
package exports:
https://repository.apache.org/content/groups/snapshots/org/apache/felix/org.apache.felix.fileinstall/3.5.3-SNAPSHOT/org.apache.felix.fileinstall-3.5.3-20160401.145250-1.jar
.

I'm going to open a cross-community thread to enquire.

Cheers,

*Raúl 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=email&utm_medium=email&utm_campaign=apache> |
twitter: @raulvk <https://twitter.com/raulvk>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message