-
Notifications
You must be signed in to change notification settings - Fork 534
Artifacts should be OSGi enabled #158
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
Milestone
Comments
Yeah it's going to be this plugin, though I'm a bit confused how exactly to use it (spent 10mins or so on it, so not too much yet..). // cc @alkemist? |
There seems to be a bit of issues with it? |
ktoso
added a commit
to ktoso/reactive-streams
that referenced
this issue
Nov 27, 2014
ktoso
added a commit
to ktoso/reactive-streams
that referenced
this issue
Nov 27, 2014
ktoso
added a commit
to ktoso/reactive-streams
that referenced
this issue
Nov 27, 2014
ktoso
added a commit
to ktoso/reactive-streams
that referenced
this issue
Nov 27, 2014
The built in OSGi plugin should be adequate for these modest needs. |
ktoso
added a commit
to ktoso/reactive-streams
that referenced
this issue
Nov 28, 2014
Fixed by @alkemist with the new Gradle build |
Wohoo! :-) Thanks @alkemist |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is required for use in OSGi containers and, since this is an API, for any OSGI-enabled implementer of that API. Lack of OSGi support is a blocker for use of Reactive Streams in Slick (which publishes OSGI-enabled artifacts).
I have a working version in https://github.com/szeiger/reactive-streams/compare/osgi-test but this is based on the sbt build which was unfortunately just abandoned. I am clueless when it comes to Gradle.
The text was updated successfully, but these errors were encountered: