This is, I think, the biggest problem with OSGI for me at least. The maven dependency model is different from OSGI (classloaders work differently, so some packages will just not work. Also implied classes from JDKs etc are "just there" seemingly when using maven + a JDK to run things) and the maven-bundle-plugin does not automatically convert from maven bundles to something useable in osgi. This is not possible generally for it, but it feels as if it could still be improved slightly.
I actually use guava in OSGI though, and did not have this particular problem. I might have been using a pre-realease maven-bundle-plugin, but dont think the guava was a specific osgi-bundle. On Wed, Jan 12, 2011 at 15:13, Clay McCoy <[email protected]> wrote: > The whole reason that I am trying to use Embed dependencies and transitive > = > true is so that I don't have to deal with dependencies. They are all > supposed to be embedded into a self contained jar. > But now I am having to deal with sun.misc. This seems like a conceptual > flaw with the plugin or a misconception on my part. > > On Tue, Jan 11, 2011 at 5:45 PM, Justin Edelson <[email protected] > >wrote: > > > The system bundle is described in section 4.6 of the OSGi core spec. > > > > On Jan 11, 2011, at 6:36 PM, Clay McCoy <[email protected]> wrote: > > > > > What is the system bundle? > > > I don't know what guava needs, and I don't want to. > > > > > > On Jan 11, 2011 5:09 PM, "Justin Edelson" <[email protected]> > > wrote: > > > > > > If this package is necessary for guava to operate, you should add it to > > the > > > system bundle's exports. > > > > > > Justin > > > > > > On Jan 11, 2011, at 6:04 PM, Clay McCoy <[email protected]> wrote: > I > > have a > > > dependency on guava a... > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- John Bäckstrand
