-
Notifications
You must be signed in to change notification settings - Fork 967
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
Publish with stable JDK9 module name #546
Milestone
Comments
jroper
added a commit
to jroper/config
that referenced
this issue
Feb 21, 2018
Fixes lightbend#546. Adds Automatic-Module-Name: typesafe.config, rather than defaulting to the very generic module name of config that the JVM selects.
ktoso
pushed a commit
that referenced
this issue
Feb 21, 2018
Fixes #546. Adds Automatic-Module-Name: typesafe.config, rather than defaulting to the very generic module name of config that the JVM selects.
@ktoso can you add a note to NEWS.md ? ( release steps in https://github.com/lightbend/config/blob/master/CONTRIBUTING.md of course) thanks! |
Man, sorry for missing process, will follow up steps |
aalleexxeeii
pushed a commit
to aalleexxeeii/typesafe-config
that referenced
this issue
Jun 6, 2018
Fixes lightbend#546. Adds Automatic-Module-Name: typesafe.config, rather than defaulting to the very generic module name of config that the JVM selects.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Typesafe config currently gets an automatic module name of
config
, since the artifact name is config. This is a recipe for conflict. This can be solved by adding anAutomatic-Module-Name
attribute to the jar manifest. I suggest we name itcom.typesafe.config
, or justtypesafe.config
.The text was updated successfully, but these errors were encountered: