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.

Sign up for GitHub

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

Jump to bottom

3.0.0-RC3 jars don't export packages via OSGi headers #6671

Closed
io7m opened this issue Oct 16, 2019 · 3 comments
Closed

3.0.0-RC3 jars don't export packages via OSGi headers #6671

io7m opened this issue Oct 16, 2019 · 3 comments
Labels
3.x Build
Milestone
3.0

Comments

@io7m
Copy link
Contributor

io7m commented Oct 16, 2019

Hello!

I've noticed that the 3.0.0-RC* artifacts on Maven Central don't export any packages via their OSGi headers despite actually having full OSGi metadata (note that all of the packages are there as Private-Package declarations):

Manifest-Version: 1.0
Automatic-Module-Name: io.reactivex.rxjava3
Bnd-LastModified: 1568707123117
Bundle-Description: Reactive Extensions for the JVM – a library for 
 composing asynchronous and event-based programs using observable sequ
 ences for the Java VM.
Bundle-DocURL: https://github.com/ReactiveX/RxJava
Bundle-ManifestVersion: 2
Bundle-Name: rxjava
Bundle-SymbolicName: rxjava
Bundle-Vendor: RxJava Contributors
Bundle-Version: 3.0.0.RC3
Created-By: 1.8.0_222 (Private Build)
Eclipse-ExtensibleAPI: true
Import-Package: org.reactivestreams;version="[1.0,2)"
Private-Package: io.reactivex.rxjava3.annotations,io.reactivex.rxjava3
 .core,io.reactivex.rxjava3.disposables,io.reactivex.rxjava3.exception
 s,io.reactivex.rxjava3.flowables,io.reactivex.rxjava3.functions,io.re
 activex.rxjava3.internal.disposables,io.reactivex.rxjava3.internal.fu
 nctions,io.reactivex.rxjava3.internal.fuseable,io.reactivex.rxjava3.i
 nternal.observers,io.reactivex.rxjava3.internal.operators.completable
 ,io.reactivex.rxjava3.internal.operators.flowable,io.reactivex.rxjava
 3.internal.operators.maybe,io.reactivex.rxjava3.internal.operators.mi
 xed,io.reactivex.rxjava3.internal.operators.observable,io.reactivex.r
 xjava3.internal.operators.parallel,io.reactivex.rxjava3.internal.oper
 ators.single,io.reactivex.rxjava3.internal.queue,io.reactivex.rxjava3
 .internal.schedulers,io.reactivex.rxjava3.internal.subscribers,io.rea
 ctivex.rxjava3.internal.subscriptions,io.reactivex.rxjava3.internal.u
 til,io.reactivex.rxjava3.observables,io.reactivex.rxjava3.observers,i
 o.reactivex.rxjava3.parallel,io.reactivex.rxjava3.plugins,io.reactive
 x.rxjava3.processors,io.reactivex.rxjava3.schedulers,io.reactivex.rxj
 ava3.subjects,io.reactivex.rxjava3.subscribers
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.6))"
Tool: Bnd-4.2.0.201903051501

Is there some reason for this?
@akarnokd
Copy link
Member

Tool: Bnd-4.2.0.201903051501

Gradle stopped supporting the OSGi plugin and this is what the suggested replacement, BND, does. I have no idea how to configure it.

PR welcome.

@io7m
Copy link
Contributor Author

io7m commented Oct 16, 2019

Ah, yes, this happened to another project I'm vaguely involved with. Thankfully it's easily fixed. I should have a PR by the end of the week.

@akarnokd akarnokd added this to the 3.0 milestone Oct 16, 2019
@io7m io7m mentioned this issue Oct 17, 2019
Merged
akarnokd pushed a commit that referenced this issue Oct 17, 2019
@io7m @akarnokd
Add Export-Package declarations for OSGi headers (#6675)
c84af61 
This adds the necessary declarations to the Bnd plugin to export all
non-internal packages for use in an OSGi environment.

Affects: #6671
@akarnokd
Copy link
Member

Closing via #6675

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.x Build
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
2 participants
@io7m @akarnokd