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
Fixes #367: generate a JPMS module descriptor #370
Conversation
That'd be good, although I think in JPMS land you should not append a version but just use |
Can you please remove the spaces/tabs commit? |
I'm confused about the value of moving the internal classes to |
@ppkarwasz I appreciate your effort here, but please minimize the contents of the PR to the absolute minimum. Thanks! |
many thanks @nitsanw for the quick review!! |
This commit enables the automatic generation of a JPMS module descriptor together with a matching OSGI manifest.
Hi @nitsanw, I refactored the PR to the bare minimum: the
OSGI-wise it doesn't make sense: since the other artifacts in this repo use classes from the The advantage appears on the JPMS side: using the |
@jponge: I just copied the result of |
@franz1981 note that a 4.0.2 with a |
I've checked this PR, the generated
|
@franz1981 it's on my todo list :-) I hope to release in the next couple of weeks |
@nitsanw If I can help you somehow, just ping me via email (I've sent you an email some time ago, so you'll likely see that one too ;) ) that I will happily help |
Until now
jctools-core
used the Apache Felix Maven Bundle Plugin to generate its OSGI descriptor.This PR:
org.jctools.util.internal
. If needed this package can be exported to other JCTools artifacts using the@ExportTo
annotation from BND.org.jctools.util.internal
). The OSGI descriptor becomes:module-info.class
JPMS descriptor, which is in sync (cf. JPMS libraries) with the OSGI descriptor:This descriptor can be generated by JDK 8.