8278185: Custom JRE cannot find non-ASCII named module inside

[toshiona]

I'd like to backport this to jdk17 since it fixes jlink issue with non-ASCII named module. Fix is low risk and applies cleanly. tier1 and tier2 tests have no regression with the patch.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8278185: Custom JRE cannot find non-ASCII named module inside

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/177/head:pull/177
$ git checkout pull/177

Update a local copy of the PR:
$ git checkout pull/177
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/177/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 177

View PR using the GUI difftool:
$ git pr show -t 177

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/177.diff

[bridgekeeper]

👋 Welcome back tnakamura! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@toshiona This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8278185: Custom JRE cannot find non-ASCII named module inside

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 6650652: 8281460: Let ObjectMonitor have its own NMT category

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (d4ab6566)

[GoeLin]

@toshiona, Please enable github actions for this repo.

[toshiona]

@GoeLin Thank you for teaching that. Enabled it. I hope my setting is correct.

[toshiona]

/integrate

[openjdk]

@toshiona
Your change (at version d4ab656) is now ready to be sponsored by a Committer.

[toshiona]

Got approval. May I ask someone sponsor this fix?

[phohensee]

/sponsor

[openjdk]

Going to push as commit df5a29c.
Since your change was applied there has been 1 commit pushed to the master branch:

• 6650652: 8281460: Let ObjectMonitor have its own NMT category

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @toshiona Pushed as commit df5a29c.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[toshiona]

@phohensee Thank you for your help!