> Please review this extension to #22609 which now disallows `ALL-MODULE-PATH` > without explicit `--module-path` option or a non-existent module path. In > addition, this fixes a bug mentioned in #22609 when `ALL-MODULE-PATH` and > `--limit-modules` are used in combination. It failed earlier and passes now > due to alignment of `ModuleFinder`s. With this patch JEP 493 enabled builds > and regular JDK builds behave the same in terms of `ALL-MODULE-PATH`. > > When an explicit module path is being added, there is no difference. All > modules on that path will be added as roots. Tests have been added for the > various cases and existing tests updated to allow for them to run on JEP 493 > enabled builds. Thoughts? > > Testing: > - [x] GHA, `test/jdk/tools/jlink` (all pass) > - [x] Added jlink test.
Severin Gehwolf has updated the pull request incrementally with one additional commit since the last revision: Don't allow --limit-modules with ALL-MODULE-PATH ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22494/files - new: https://git.openjdk.org/jdk/pull/22494/files/4135dcb1..f488c637 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22494&range=12 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22494&range=11-12 Stats: 48 lines in 3 files changed: 7 ins; 26 del; 15 mod Patch: https://git.openjdk.org/jdk/pull/22494.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22494/head:pull/22494 PR: https://git.openjdk.org/jdk/pull/22494
