New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netty-transport-native-epoll-*-linux-x86_64.jar is not OSGi bundle #5119
Comments
|
@MilosFabian we love PRs.. so maybe you can provide one as I don't have any good OSGI knowledge :( |
|
Alright, I will work on it :) |
|
Thanks ❤️!
|
|
I am sorry for a delay...finally I found some time take a look at it. java.lang.ClassNotFoundException: io.netty.channel.epoll.NativeStaticallyReferencedJniMethods More investigation needed. |
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to to attach manifest to jar with native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing netty#5119
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to attach manifest to the jar with a native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing netty#5119
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to attach manifest to the jar with a native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing #5119
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to attach manifest to the jar with a native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing #5119
|
Fixed by #5326 |
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to attach manifest to the jar with a native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing netty#5119
- After updating Netty 4.0 version, we sometimes see java.lang.NoClassDefFoundError: io/netty/util/internal/TypeParameterMatcher with backtrace insisting there's some dynamic class resolution inside Netty. It might be side-effect of recent native-epoll support inside karaf? netty/netty#5119 - Add DynamicImport-Package for io.netty to allow deferred wiring http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.html#how-to-provide-optional-services - Add a way to pass DynamicImport-Package on BUCK build Change-Id: I50ec3400e940c56fb52563d84659ebb30c302235
Motivation: Currenlty, netty-transport-native-epoll-*-linux-x86_64.jar is not packed as OSGi bundle and thus not working in OSGi environment. Modifications: In netty-transport-native-epoll's pom.xml added configuration to attach manifest to the jar with a native library. In netty-common's pom.xml added configuration instruction (DynamicImport-Package) to maven bnd plugin to make sure the native code is loaded from netty-transport-native-epoll bundle. Result: The netty-transport-native-epoll-*-linux-x86_64.jar is a bundle (MANIFEST.MF attached) and the inluced native library can be successfuly loaded in OSGi environment. Fixing netty#5119
Hello,
basically, reopening #3781
I am working on OpenDaylight project and we would like use netty-transport-native-epoll due to the TCP MD5 signature support. Currently we are using Netty version 4.0.33.Final and bumping to 4.0.36.Final right now.
Unfortunately, netty-transport-native-epoll-*-linux-x86_64.jar is not a bundle and since the OpenDaylight is running in OSGi container (Apache Karaf) we are not able use it directly as a bundle (like other Netty artifacts).
It would be great for us if the jar is packed as a bundle as well.
Thanks,
Milos Fabian
The text was updated successfully, but these errors were encountered: