Yes it's a kind of split package but I didn't define a merge policy (I don't know what a merge policy is).
Is it possible to do so with the maven-bundle-plugin? Regards, JP -----Message d'origine----- De : Jean-Baptiste Onofré [mailto:[email protected]] Envoyé : jeudi 6 octobre 2016 15:42 À : [email protected] Objet : Re: Strange issue on strange use case I think we are in the case of a split package. Did you define any merge policy ? Regards JB On 10/06/2016 03:40 PM, CLEMENT Jean-Philippe wrote: > I renamed the package of b.jar to something like "other.package". All is back > to normal even with BF. > > So it seems there is a bug somewhere. In OSGi, are several packages with the > same name (but with different content) allowed? > > JP > > -----Message d'origine----- > De : CLEMENT Jean-Philippe > [mailto:[email protected]] > Envoyé : jeudi 6 octobre 2016 14:28 > À : [email protected] > Objet : Strange issue on strange use case > > Hello, > > I experience a strange issue on a strange use case using Karaf 4.0.7. > > I have: > * a bundle A which wraps a jar "a.jar" and exposes a package > "some.package" (which is inside the "a.jar") > * a bundle B which contains and use a jar "b.jar" which contains a > package "some.package" (same package as "a.jar" but inside the > "b.jar") > > Until then everything is fine. All works as expected. > > I add a bundle B fragment (BF). Then bundle B crashes with a > ClassNotFoundException on a class which is contained in the b.jar. When I > remove the FB fragment, everything goes back to normal. > > Any idea on what's going on? > > JP > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
