Hi Benson, On Thu, 2014-12-11 at 12:38 -0500, Benson Margulies wrote: > So, here I am, setting up an application that embeds Felix. I need it > to contain a certain collection of bundles -- and then some > dependencies of those bundles. > > Plain-old-maven can't help very much with managing those dependencies, > since it can only deal with one version per Group/Artifact, and I > expect to have cases where we need more than one major version of some > things (e.g. Guava). > > is there a commonly-used solution to all of this? I'm contemplating > writing a Maven plugin, but I would like to avoid recreating the > wheel.
In the Apache Sling project we have a concept called 'slingstart' which allows you define the artifacts that you want to package and also OSGi configs that you want to include by default. You can see some samples at [1]. There's a Maven plugin for that as well at [2] . Another option that I've used - but only for demo purposes so far - is Pax Runner [3]. It's advertised mostly as a development-time tool, but with a little tweaking it can be used to generate deployment packages. Cheers, Robert [1]: https://svn.apache.org/repos/asf/sling/trunk/tooling/support/provisioning-model/src/test/resources/ [2]: https://svn.apache.org/repos/asf/sling/trunk/tooling/maven/slingstart-maven-plugin/ [3]: https://ops4j1.jira.com/wiki/display/paxrunner/Pax+Runner --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
