define JPMS module names #106
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Djaytan
force-pushed
the
build/define-jpms-module-names
branch
from
59bb4fa to
c8eae6a
Compare
_This change is similar to https://github.com/Incendo/cloud/pull/787_ ## Summary The goal of this change is to encourage Gradle to put the framework's Jar files in the module path instead of the classpath. For that, we need to explicitly define the `Automatic-Module-Name` attribute in the `MANIFEST.MF` files in framework's Jar files (source: https://docs.gradle.org/current/userguide/java_library_plugin.html#using_libraries_that_are_not_modules). The newly added attribute follows this format: `<groupId>.<moduleName>` (e.g. `org.incendo.cloud.paper`). Details about this change can be found here: Incendo/cloud#785. ## Impact There is no impact nor on maintainer side nor or consumer one not relying on JPMS. For the ones already relying on JPMS (e.g. Maven users), they will just have to adapt the references in their `module-info.java` files as follow: From: ```java module my.module { [...] requires cloud.paper; [...] } ``` To: ```java module my.module { [...] requires org.incendo.cloud.paper; [...] } ```
Djaytan
force-pushed
the
build/define-jpms-module-names
branch
from
c8eae6a to
63ad869
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is similar to Incendo/cloud#787
Summary
The goal of this change is to encourage Gradle to put the framework's Jar files in the module path instead of the classpath. For that, we need to explicitly define the
Automatic-Module-Nameattribute in theMANIFEST.MFfiles in framework's Jar files (source: https://docs.gradle.org/current/userguide/java_library_plugin.html#using_libraries_that_are_not_modules).The newly added attribute follows this format:
<groupId>.<moduleName>(e.g.org.incendo.cloud.paper).Details about this change can be found here: Incendo/cloud#785.
Impact
There is no impact nor on maintainer side nor or consumer one not relying on JPMS.
For the ones already relying on JPMS (e.g. Maven users), they will just have to adapt the references in their
module-info.javafiles as follow:From:
To: