As this package is only referenced from within SPI, couldn't we just exclude it
from the package exports?
Chris
Am 31.03.20, 15:17 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:
Hi,
the issue is that if we export it, then we break Nettys OSGi integration as
we get a split package situation (two bundles exporting the same package, which
is forbidden in OSGi).
So I see no easy solution (but had to do the same once as Netty is
pretty... private).
J
Am 31.03.20, 15:15 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
Hi all,
I just discussed this issue with Etienne and I thought it was important
for all, so I asked him to bring it here.
In my effort to get the EmbeddedChannel working as a full "transport"
module, I had to override the Netty Bootstrap mechanism.
Unfortunately in order to do so, I need to call "init" from the derived
class. Unfortunately this is package private in Netty so I had
To add it to the same package.
Would it help to just not export these packages to OSGi?
But I'm also open for alternatives (Please none involving mega-evil
reflection hackery).
Chris
Am 31.03.20, 15:10 schrieb "Etienne Robinet" <erobi...@apache.org>:
Hi all,
I've been working on the Camel Component and decided to test it
inside Karaf, but I noticed that I've got this error now:
https://i.imgur.com/kUZPwZ5.png
Seems like this class is not exported by the bundle so it can not
be found. Anyone has an idea on how we could solve this?
Etienne
