It's what I meant: the parent pom (via a plugin) could create the
osgi.bnd file for the user (even if it's a simple one).
Regards
JB
On 12/16/2015 04:44 PM, Christian Schneider wrote:
We could of course also put all the apis in the parent.
Unfortunately a pom can not provide a osgi.bnd. So for now if we want to
use it and I think it makes sense you have to create it. We should be
able to change that though.
Christian
On 16.12.2015 16:38, Jean-Baptiste Onofré wrote:
I see your point about starter. maybe just karaf-boot ? So we can have
karaf-boot, karaf-boot-core, and karaf-boot-parent ?
For the osgi.bnd, if the karaf-boot (aka
karaf-boot-starter/karaf-boot-api) can provide a default one, it's
fine for me.
We will provide an archetype, but anyway, the purpose of karaf-boot is
also to be able to start very quickly: so a very basic pom.xml just
defining karaf-boot-parent should be enough.
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
