I also got some troubles when (quick) testing the felix bundle-plugin : I have configured the maven-jar-plugin to set some custom MANIFEST entries (in my case, the SVN revision number as Build-Revision). When using the felix plugin, my MANIFEST is replaced by OSGi one, not merged.
But maybe I missed some configuration ? Or maybe this requires enhancement in the bundle plugin ? That beeing said, thanks to this plugin, making a m2 project OSGi compliant seems really easy as many of the required meta-datas are allready available in pom. I think this is a good point in OSGi adoption. Nico. 2007/12/20, Carsten Ziegeler <[EMAIL PROTECTED]>: > > Thanks for the very positive response so far! Great! > > I'll come up with some patches for some of the commons projects; there > is a minor problem as the current commons parent pom defines the > manifest entries, but I think that we can come up with a solution for > this. > > Carsten > > -- > Carsten Ziegeler > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
