New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8282444: Module finder incorrectly assumes default file system path-separator character #7632
8282444: Module finder incorrectly assumes default file system path-separator character #7632
Conversation
|
@ChrisHegarty The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
The update to ModulePath looks okay. The tests for ModulePath with paths to locate files in custom file systems are somewhat minimal and probably should be expanded to ensure that there aren't any other issues. Updating the existing ModulesInCustomFileSystem test to use a deeper package structure is subtle but okay for now but we should create another issue to create more tests for custom file systems. I assume you'll update the date in the copyright header of the changed files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Chris, maybe you should add @bug 8282444
to ModulesInCustomFileSystem.java
too?
The downside is that it would make it look like the test was added fro this issue. I think it only works if the original issue for the module system implementation is there too. |
Yeah, that's a good point. I'll take a closer look at this and see how best to expand the coverage (separately).
Done.
I added a tag with both the original bugId that introduced the test, 8178380, and bug Fix Id for this issue, 8282444. |
@ChrisHegarty This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
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 no new commits pushed to the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an expert of the area but the proposed changes look good to me.
/integrate |
Going to push as commit 369291b.
Your commit was automatically rebased without conflicts. |
@ChrisHegarty Pushed as commit 369291b. |
The module finder implementation incorrectly uses the path-separator
character from the default file system, when mapping the relative path
of an entry in an exploded module to a package name. This causes
problems on Windows [*] when using a module finder with a custom file
system that has a path-separator character that differs from that of the
default file system, e.g. the zip file system (which uses '/',
rather than '\' ).
Rather than adding a new test for this, I deciced to just modify an
existing one. The existing test exercises the module finder with a
custom file system, but does so with modules have trivial single-level
packages names. I just expanded the module to have a subpackage. This
is sufficient to reproduce the bug, and verify the fix.
[*]
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7632/head:pull/7632
$ git checkout pull/7632
Update a local copy of the PR:
$ git checkout pull/7632
$ git pull https://git.openjdk.java.net/jdk pull/7632/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7632
View PR using the GUI difftool:
$ git pr show -t 7632
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7632.diff