On Thu, 27 Aug 2026 10:59:02 GMT, Yunbo Zhang <[email protected]> wrote:
>> Problem: >> >> When `-bootclasspath` is specified, javap still searches `SYSTEM_MODULES` >> before `PLATFORM_CLASS_PATH`. Therefore, system classes such as >> `java.lang.Object` are loaded from the current JDK instead of the specified >> boot class path. >> >> Fix: >> >> When a boot class path is explicitly specified, skip the `SYSTEM_MODULES` >> lookup. The existing behavior remains unchanged otherwise. >> >> Testing: >> >> - Added regression coverage for all three boot class path option forms: >> `-bootclasspath`, `--boot-class-path`, and `--boot-class-path=<path>`. >> - `make test TEST=test/langtools/tools/javap`: 87 passed, 1 excluded, 0 >> failed. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Yunbo Zhang has updated the pull request with a new target base due to a > merge or a rebase. The pull request now contains one commit: > > 8354563: javap's -bootclasspath option is no longer respected test/langtools/tools/javap/BootClassPathTest.java line 3: > 1: /* > 2: * Copyright (c) 2026, Oracle and/or its affiliates. All rights reserved. > 3: * Copyright (c) 2026, Yunbo Zhang. All rights reserved. Hello @benshuai5D, the copyright headers in the JDK files aren't expected to have individual user names. Please remove this line. The OpenJDK guide has some details how individuals retain copyright interests in the code https://openjdk.org/guide/#sign-the-oca. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32554#discussion_r3874128852
