this happens and how to resolve? thx.
--
View this message in context:
http://karaf.922171.n3.nabble.com/exported-package-in-bundle-A-is-not-able-to-be-imported-in-bundle-B-tp4046019.html
Sent from the Karaf - User mailing list archive at Nabble.com.
the one expected
> bundle which is exported same package (I've triple-checked the manifest.mf
> files for both bundles in data/cache/xyz). i.e. there is no split-package
> problem in this scenario afaik.
>
> Any idea how/why this happens and how to resolve? thx.
>
>
>
tClass=com.foo.bar.myClass)
> >
> > When I run package:exports | grep com.foo.bar I see only the one expected
> > bundle which is exported same package (I've triple-checked the
> manifest.mf
> > files for both bundles in data/cache/xyz). i.e. there is no
> split
t;> (objectClass=com.foo.bar.myClass)
>>
>> When I run package:exports | grep com.foo.bar I see only the one expected
>> bundle which is exported same package (I've triple-checked the
>> manifest.mf
>> files for both bundles in data/cache/xyz). i.e. there is n
un(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> Missing dependencies:
>>> (objectClass=com.foo.bar.myClass)
>>>
>>> When I run package:exports | grep com.foo.bar I see only the one expected
>>> bu
.922171.n3.nabble.com/exported-package-in-bundle-A-is-not-able-to-be-imported-in-bundle-B-tp4046019p4046045.html
Sent from the Karaf - User mailing list archive at Nabble.com.
