Pass the target release to plexus-java when resolving module descriptors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- build-system
Research direction
Start in CompilerMojo and TestCompilerMojo, and trace how release and target are selected for --patch-module in #1137. Inspect the ResolvePathsRequest release setting from plexus-languages#237, then verify that both compiler paths pass release with target as fallback. Done means module descriptors are resolved for the configured execution version rather than the running JDK.
Written by the indexing model from the issue text.
Description
New feature, improvement proposal
When a module descriptor comes from META-INF/versions/<N> of a multi-release jar or output directory, plexus-java picks <N> from the JDK running Maven rather than from the execution's release/target. Maven 3.9 on JDK 8 compiling through a Java 9+ toolchain therefore never sees such descriptors, and a newer runtime can pick one above the configured release.
Once codehaus-plexus/plexus-languages#237 adds a release setting to ResolvePathsRequest, CompilerMojo and TestCompilerMojo should set it from release, falling back to target, the same version the plugin already uses to choose the directory for --patch-module (#1137).
- Dominant language
- Java
- Stars
- 263
- Forks
- 195
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/maven-compiler-plugin
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/maven-compiler-plugin#1148 · 2 comments ·
Maintainers usually reply within 1 day
-
3.x bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/maven-compiler-plugin#1140 · 1 comment ·
Maintainers usually reply within 1 day
-
3.x bug
Difficulty 4/5 3-5 days Newbie friendliness 64/100
apache/maven-compiler-plugin#1137 ·
Maintainers usually reply within 1 day
-
3.x bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/maven-compiler-plugin#1124 · 1 comment · 3 reactions ·
Maintainers usually reply within 1 day
-
build github_actions
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/maven-compiler-plugin#1099 ·
Maintainers usually reply within 1 day
All issues in apache/maven-compiler-plugin
Similar issues
-
pdfium-drift
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Stirling-Tools/JPDFium#176 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiero-ledger/hiero-consensus-node#27712 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Vakore/ZappierGames#162 ·
-
Improve README documentation clarity and fix minor wording issuesPossibly taken @simplesilence claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
resilience4j/resilience4j#2567 ·
Maintainers usually reply within 6 days
-
Priority/High
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
wso2/dpdp-accelerator#417 ·
Maintainers usually reply within 1 day