Hopefully you are not using any require-bundle headers. So you can think in terms of package requirements rather than bundle dependencies. OBR is pretty much the solution to this, but AFAIK there is no reasonable way to automate figuring out what set of bundles should be in your repository. IIRC some versions of nexus (maybe all by now) can generate an xml file for obr, but I don't think running obr against maven central is likely to produce results you are happy with.
After being a maven fanatic for many years I now think the impedance mismatches between maven and osgi are pretty large and given a free hand with a project would probably use a gradle + bndtools build with a local file system repository (generally under "cnf" in these builds IIUC for reasons I don't know). hopefully I haven't misunderstood your question too much... david jencks On Dec 11, 2014, at 12:38 PM, Benson Margulies <ben...@basistech.com> 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
