2009/3/20 <[email protected]> > Hello, > > I have a bundle 'a' with the class a.A, a bundle 'b' with the class b.B > (which extends a.A), and a bundle 'c' with the class c.C (which extends > b.B). > > The manifest of b, generated with the maven-bundle-plugin, says: > Export-Package: b;uses:=a > Import-Package: a,b > > while the manifest of c, also generated with the maven-bundle-plugin, > says: > Export-Package: c;uses:=b > Import-Package: b,c > > Now, when I use these bundles in Eclipse, I get errors with the bundle c: > "The project was not built since its build path is incomplete" and "The > type a.A cannot be resolved. It is indirectly referenced from required > .class files". > > I'm wondering who is right: Eclipse or maven-bundle-plugin? >
I believe Eclipse/PDE is at fault, see the following bugs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=180629 https://bugs.eclipse.org/bugs/show_bug.cgi?id=122915 which are still open after more than 3 years :( the quick way to make sure is to try installing the bundles on an OSGi framework - say either Felix / Equinox / Knopflerfish Pax-Runner can help you switch quickly between frameworks: http://wiki.ops4j.org/display/ops4j/Pax+Runner I often try testing bundles on a number of frameworks to make sure I'm not relying on any specific / non-standard behaviour HTH Thanks > > -- clovis > > > ______________________________________ > Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. > Wenn diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns > unverzueglich zu informieren und sie zu loeschen. > > This e-mail message may contain information, which is confidential and > protected. If you are not the intended recipient of this message, we ask you > to inform us immediately and delete the message afterwards. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Stuart
