-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Add OSGi Metadata #29
Comments
Hi! thanks for this! Seem OK. although I'm not sure if changing the packaging from jar to bundle can affect anyone. Don't have lots of experience with OSGi. |
It has been a while since this. I will close this for now as it seems no one need this. Will glad to reopen this if people ask for this. |
Hi, |
Hi! |
@stibi I created that as a result of this issue. I'd be happy to push to maven central but just need to agree how to credit Jedis in the release notes. You've also seen the Jedis Karaf / Gogo shell commands bundle in my repo too I guess ? |
@sneakybeaky Hi! Yes I noticed Jedis Karaf shell too, nice! I'll definitely check it out! Thanks! |
@sneakybeaky This is not the best place for such discussion, but I need to ask you for help, with quite basic problem I have, right from the start… |
@stibi look at https://github.com/sneakybeaky/osgi-leaderboards#getting-started, specifically the part about editing the org.ops4j.pax.url.mvn.cfg file. Once done you can add the jedis feature :
An example of using blueprint to define a local redis datasource can be found at https://github.com/sneakybeaky/jedis-osgi/blob/master/example-datasource/src/main/resources/OSGI-INF/blueprint/local-redis-datasource.xml |
ok, thanks for the repository url…
was working for me. |
You'll need apache commons pool too:
|
It would be nice if this library would ship with a valid MANIFEST.MF for OSGi Bundle compatibility.
This is quite simple to achieve and would make jedis OSGi compatible (broaden the audience, make it a first class citizen in Java App Severs that leverage OSGi as Runtime already.. and so on).
(fork commit coming)
The text was updated successfully, but these errors were encountered: