Skip to content
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

OSGi : Wrong mainfest data in hazelcast-all 2.5.1 #484

Closed
lburgazzoli opened this issue May 23, 2013 · 2 comments

Comments

Projects
None yet
3 participants
@lburgazzoli
Copy link

commented May 23, 2013

The bundle hazelcast-all 2.5.1 declares com.hazelcast.instance as Import-Package :

Import-Package = 
        ...
        com.hazelcast.instance,
        ...

Thus the bundle cannot be started in OSGi containers like Karaf:

karaf@kha-1> la | grep 430
[ 430] [Installed  ] [            ] [   80] hazelcast-all (2.5.1)
karaf@kha-1> start 430
Error executing command: Error starting bundles:
        Unable to start bundle 430: Unresolved constraint in bundle com.hazelcast.all [430]: Unable to resolve 430.0: missing requirement [430.0] osgi.wiring.package; (osgi.wiring.package=com.hazelcast.instance)
@MrEasy

This comment has been minimized.

Copy link
Contributor

commented May 23, 2013

I can confirm this misbehavior.
However, I compiled the 2.5.1 tag myself and my manifest did not contain the problematic Import-Package statement - weird, but I did not look deeper into it.

@lburgazzoli

This comment has been minimized.

Copy link
Author

commented May 23, 2013

In the meantime I've compiled the 2.5.2.SNAPSHOT and the Import-Package does not list com.hazelcast.instance as requirement.

@mdogan mdogan closed this Jun 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.