Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 25
Affects Version/s: 24, 25
Component/s: tools
Labels:
- hgupdate-sync
- release-note=yes

Subcomponent:
jlink
Resolved In Build:
b04

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8348488	24.0.1	Severin Gehwolf	P3	Resolved	Fixed	b04
JDK-8347333	24	Severin Gehwolf	P3	Resolved	Fixed	b32

When using jlink with the --add-modules ALL-MODULE-PATH the --module-path option should be required. This currently silently passes, since the default module path (the jmods directory of the JDK installation) is being added when jlink runs. It's problematic in terms of consistency for JEP 493 enabled builds.

backported by

JDK-8347333 Disallow ALL-MODULE-PATH without explicit --module-path

Resolved

JDK-8348488 Disallow ALL-MODULE-PATH without explicit --module-path

Resolved

csr for

JDK-8345894 Disallow ALL-MODULE-PATH without explicit --module-path

Closed

is blocked by

JDK-8345573 Module dependencies not resolved from run-time image when --limit-module is being used

Resolved

relates to

JDK-8189777 jlink --module-path default value and automatic addition of $JAVA_HOME/jmods if java.base is missing

Resolved

JDK-8346739 jpackage tests failed after JDK-8345259

Closed

JDK-8311302 Implement JEP 493: Linking Run-Time Images without JMODs

Resolved

links to

Commit(jdk24) openjdk/jdk/7d4fa781

Commit(master) openjdk/jdk/bcb1bdaa

Review(jdk24) openjdk/jdk/22849

Review(master) openjdk/jdk/22494

(2 relates to, 4 links to)

Release Note: jlink --add-modules ALL-MODULE-PATH Requires Explicit --module-path Argument

Resolved

Severin Gehwolf

Assignee:: Severin Gehwolf
Reporter:: Severin Gehwolf
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: 2024-11-29 07:44
Updated:: 2025-01-23 17:12
Resolved:: 2024-12-20 04:37

Details

Backports

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates