We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be great if a stable JPMS module name can be provided, as simply as adding Automatic-Module-Name to the manifest in the jar.
Automatic-Module-Name
This will allow projects that are moving to proper JPMS modules to reference a stable JPMS name for jnr-unixsocket in their module-info.java.
jnr-unixsocket
module-info.java
I would suggest to not use com.github as prefix, but perhaps just org.jnr, but it's ultimately your choice.
com.github
org.jnr
Thanks!
The text was updated successfully, but these errors were encountered:
Also, jnr-unisocket has a split package with jnr-enxio: jnr.enxio.channels.
jnr-unisocket
jnr-enxio
jnr.enxio.channels
This makes impossible to use jnr-unixsocket as JPMS module, even adding the Automatic-Module-Name entry.
Sorry, something went wrong.
Fixed along with #58.
No branches or pull requests
Would be great if a stable JPMS module name can be provided, as simply as adding
Automatic-Module-Name
to the manifest in the jar.This will allow projects that are moving to proper JPMS modules to reference a stable JPMS name for
jnr-unixsocket
in theirmodule-info.java
.I would suggest to not use
com.github
as prefix, but perhaps justorg.jnr
, but it's ultimately your choice.Thanks!
The text was updated successfully, but these errors were encountered: