-
Bug
-
Resolution: Fixed
-
P4
-
11, 14, 15, 16
-
b05
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8301982 | 11.0.20-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
JDK-8307803 | 11.0.20 | Lutz Schmidt | P4 | Resolved | Fixed | b03 |
modules-deps.gmk is generated by Modules.gmk by filtering all the module-info.java files. However, if a module-info.java happens to contain \r(CR) character on Windows the filtered module name ends up with a CR on the end causing an invalid dependency build break on Windows.
Reproduce:
On Windows edit src/java.rmi/share/classes/module-info.java and
insert a CR at the end of line "requires java.logging;"
Build... will produce error like:
08:31:04 + make all
08:31:30 Building target 'all' in configuration 'windows-x86_64-server-release'
08:31:30 Compiling 8 files for BUILD_TOOLS_LANGTOOLS
08:31:30 make[2]: *** No rule to make target 'java.logging
Reproduce:
On Windows edit src/java.rmi/share/classes/module-info.java and
insert a CR at the end of line "requires java.logging;"
Build... will produce error like:
08:31:04 + make all
08:31:30 Building target 'all' in configuration 'windows-x86_64-server-release'
08:31:30 Compiling 8 files for BUILD_TOOLS_LANGTOOLS
08:31:30 make[2]: *** No rule to make target 'java.logging
- backported by
-
JDK-8301982 On Windows generated modules-deps.gmk can contain backslash-r (CR) characters
- Resolved
-
JDK-8307803 On Windows generated modules-deps.gmk can contain backslash-r (CR) characters
- Resolved