after some deep research, I ended up noticing that some dependencies I use (like jbossall-client) have themselves dependencies to many other packages. However, since we don't use those features, we don't need the dependencies in our classpath but the maven-bundle-plugin correctly detects them.
My conclusion, which is obviously stupid I admit : When developing OSGi bundles, one should really be even more careful with the libs one depends on. For exemple, when depending on jbossall-client, the OSGi bundle will also depend on Hiberate even though it is never used. Thus generating an "unresolved package" when starting the bundle. Obvious for rookies but touchy for OSGi real beginners... Elvy wrote: > > As a first step at migrating my current swing client App to OSGi, I > thought of creating a massive bundle containing my whole application. Once > done, I would start creating service interfaces and decouple my app little > by little. Seems like a reasonable migration process to me... > > I'm then trying to create this massive application bundle but keep on > struggling with "unresolved packages" > > here's the output of my shell : > _________________________________________________________________________________ > -> ps > START LEVEL 1 > ID State Level Name > [ 0] [Active ] [ 0] System Bundle (1.0.1) > [ 1] [Active ] [ 1] Apache Felix Shell Service (1.0.0) > [ 2] [Active ] [ 1] Apache Felix Shell TUI (1.0.0) > [ 3] [Active ] [ 1] Apache Felix Bundle Repository (1.0.0) > [ 8] [Installed ] [ 1] Tactical Editor Bundle (0.1.0.SNAPSHOT) > -> start 8 > org.osgi.framework.BundleException: Unresolved package in bundle 8: > package; (package=org.hibernate.loader.collection) > -> stop 8 > _________________________________________________________________________________ > > If I'm not mistaken, the only dependency I use that includes some > hibernate things is jbossall-client v4.2.0.GA. It does contain > org.hibernate.loader, but there's only one class inside and no packages. > Meanwhile, my manifest contains many references to packages inside > org.hibernate.loader. > > I would rather not specify all those dependencies as optional, I'd prefer > to understand what the real issue is. Needless to say that since all my > app is in the bundle for the moment, I'm bound to have the same problem > for other packages as well. :-( > > I feel like not controlling the manifest at all. > > Have you ever experienced something similar? > > > > > ----- Tell me something you don't know! -- View this message in context: http://www.nabble.com/Anarchy-in-Private-Package-and-Import-Package-tf4903977.html#a14073429 Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
