Skip to content

OSGi bundle resolving problems #1091

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

Closed
thjaeckle opened this issue Feb 4, 2016 · 8 comments
Closed

OSGi bundle resolving problems #1091

thjaeckle opened this issue Feb 4, 2016 · 8 comments

Comments

@thjaeckle
Copy link

Hi.
With the latest 2.0.0-RC8 there seem to be some problems with the OSGi manifests.
When trowing following bundles into into a Felix container I get 2 errors.

The Bundles

(which are transitive dependencies of async-http-client):

  • netty-transport-4.0.34.Final.jar
  • netty-handler-4.0.34.Final.jar
  • netty-common-4.0.34.Final.jar
  • netty-codec-4.0.34.Final.jar
  • netty-codec-http-4.0.34.Final.jar
  • netty-buffer-4.0.34.Final.jar
  • javassist-3.18.1-GA.jar
  • netty-reactive-streams-1.0.2.jar
  • async-http-client-2.0.0-RC8.jar
  • netty-codec-dns-2.0.0-RC8.jar
  • netty-resolver-dns-2.0.0-RC8.jar
  • netty-resolver-2.0.0-RC8.jar

Error 1

2016-02-04 12:51:46,425 | WARN  | ? | org.apache.felix.fileinstall | Error while starting bundle: file:/D:/felix/osgi/deploy/netty-resolver-dns-2.0.0-RC8.jar
org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.asynchttpclient.netty-resolver-dns [105.0] because it exports package 'io.netty.channel' and is also exposed to it from bundle revision io.netty.transport [95.0] via the following dependency chain:

  org.asynchttpclient.netty-resolver-dns [105.0]
    import: (&(osgi.wiring.package=io.netty.handler.codec.dns)(version>=2.0.0)(!(version>=3.0.0)))
     |
    export: osgi.wiring.package=io.netty.handler.codec.dns; uses:=io.netty.channel.socket
  org.asynchttpclient.netty-codec-dns [102.0]
    import: (&(osgi.wiring.package=io.netty.channel.socket)(version>=4.0.0)(!(version>=5.0.0)))
     |
    export: osgi.wiring.package=io.netty.channel.socket; uses:=io.netty.channel
    export: osgi.wiring.package=io.netty.channel

Error 2

2016-02-04 12:51:46,430 | WARN  | ? | org.apache.felix.fileinstall | Error while starting bundle: file:/D:/felix/osgi/deploy/async-http-client-2.0.0-RC8.jar
org.osgi.framework.BundleException: Unresolved constraint in bundle org.asynchttpclient.async-http-client [90]: Unable to resolve 90.0: missing requirement [90.0] osgi.wiring.package; (osgi.wiring.package=com.typesafe.netty)

*Edit: the Error 2 probably is because artifact netty-reactive-streams-1.0.2.jar is no OSGi bundle (no MANIFEST exports).

@slandelle
Copy link
Contributor

Frankly, I personally have no usage for OSGI.
Contributions welcome.

@vadeg
Copy link

vadeg commented Apr 5, 2016

Hi!

Which Felix version do you use?

Could you please show output of lb command from felix command line when you get this error?

@slandelle
Copy link
Contributor

slandelle commented Apr 6, 2016

Probably related to #1132.

I'll be clear: I personally don't have a usage for OSGI. In order to fix #1132, I removed this Felix crap.
If anyone really needs OSGI support, please contribute.

@piyushGoyal2
Copy link

So no support for OSGi... super sad..!!! :(

@slandelle
Copy link
Contributor

slandelle commented Jul 20, 2016

As stated in the labels, contributions welcome.

@piyushGoyal2
Copy link

oki.. I will try to contribute soon..! :-)

@slandelle
Copy link
Contributor

Great!

@slandelle slandelle removed the AHC2 label Oct 12, 2016
@slandelle
Copy link
Contributor

Closing because of lack of activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants