It's something I don't get either, why they didn't work on the
maven-bundle-plugin, but that's something you need to ask the bnd folks.
blueprint isn't dead btw. just the website really really sucks :D

regards, Achim

2016-04-06 8:53 GMT+02:00 Claus Ibsen <claus.ib...@gmail.com>:

> On Wed, Apr 6, 2016 at 8:49 AM, Achim Nierbeck <bcanh...@googlemail.com>
> wrote:
> > Hi,
> >
> > just wanted to give my 2 cents here.
> > I'm watching the bnd-maven-plugin for a while now, from my perspective
> it's
> > not quite there yet, that's why I would stick with the
> maven-bundle-plugin
> > for a while.
> >
>
> Yeah all the sister Apache projects like Karaf / ServiceMix / CXF /
> ActiveMQ etc are also using it.
>
> Though it begs the question - why 2 plugins?
> Why cant they work together and make 1 good plugin. There adoption of
> OSGi do not need more confusion and projects that start to stall. Look
> at blueprint that is semi dead - not updated website and whatnot.
>
>
>
>
> > regards, Achim
> >
> >
> > 2016-04-06 7:46 GMT+02:00 Claus Ibsen <claus.ib...@gmail.com>:
> >
> >> Hi
> >>
> >> It all sound promising. But there is plenty of changes already for
> >> 2.18 in the build system. We should IMHO keep this version as-is to
> >> avoid too many changes. Building OSGi bundles is really complex for a
> >> project the size as Apache Camel. We need to get what we have now out
> >> to the community.
> >>
> >> Changing to a new plugin seems a bit risky to me at this stage.
> >>
> >> For the next release Camel 2.19 or what the version is, then it can be
> >> on the roadmap and then other issues we discover such as what you
> >> found that required a version 3.2.0 etc can be ironed out.
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Tue, Apr 5, 2016 at 8:58 PM, Quinn Stevenson
> >> <qu...@pronoia-solutions.com> wrote:
> >> > I’ve got the basics down for doing this conversion, but there are a
> >> couple of differences between the MANIFEST.MF files generated by the two
> >> tools when SNAPSHOT versions are used.
> >> >
> >> > Bundle-Version header:
> >> > By default, given a version in a POM like "1.2.3-SNAPSHOT”:
> >> >    - the maven-bundle-plugin converts the version to “X.X.X.SNAPSHOT"
> >> >    - the bnd-maven-plugin changes the version "X.X.X.<timestamp>"
> >> > There is a new instruction in the upcoming 3.2.0 release of the
> >> bad-maven-plugin that will allow preserving the “.SNAPSHOT” in the
> >> Bundle-Version header.
> >> >
> >> > I’m assuming we want to preserve the “.SNAPSHOT” in the Bundle-Version
> >> header, so we’ll need to wait for version 3.2.0 of the bnd-maven-plugin
> >> >
> >> > Export-Package header:
> >> >  - the maven-bundle-plugin includes “.SNAPSHOT” in the version of
> >> exported packages - i.e. org.apache.camel;version=“2.18.0-SNAPSHOT"
> >> >  - the bnd-maven-plugin does not include “.SNAPSHOT” in the version of
> >> the exported packages - i.e. org.apache.camel;version=“2.18.0”
> >> > The bad-maven-plugin can be configured to do this by adding a
> >> “packageinfo” file for every exported package
> >> >
> >> > Do we need to keep the “.SNAPSHOT” in the exported package versions?
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >
> >
> >
> > --
> >
> > Apache Member
> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
> > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
> &
> > Project Lead
> > blog <http://notizblog.nierbeck.de/>
> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
> >
> > Software Architect / Project Manager / Scrum Master
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

Reply via email to