Read the module descriptor of a multi-release output directory - #236
Merged
Merged
Conversation
slachiewicz
marked this pull request as ready for review
September 25, 2026 22:39
This was referenced Sep 25, 2026
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
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.
An output directory built with
multiReleaseOutputhas itsmodule-info.classonly underMETA-INF/versions/<N>, so a reactor sibling that has not been packaged yet was resolved as a filename-based automatic module and left on the classpath. Directories now get the same versioned lookup that multi-release jars already have. Like the jar lookup, it starts from the running JDK version, so a Java 8 runtime does not see versioned descriptors.This is the plexus-java half of apache/maven-compiler-plugin#1137; the plugin still has to put
META-INF/versions/<N>on--module-pathwith a--patch-modulefor the directory, because javac reads an exploded module only from its root.