-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b162
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8177590 | 10 | Jan Lahoda | P2 | Resolved | Fixed | b04 |
In a private email conversation, it was noted that putting all of the source of a module on the patch module path for javadoc was reported as an error. But in similar circumstances, the runtime only gives a warning.
javac should generally behave the same as the runtime in this situation.
javadoc output:
error: module-info.class not allowed on patch path: /usr/**redacted**/jdk/src/jdk9/jdk/src/java.base/share/classes/module-info.java
javac should generally behave the same as the runtime in this situation.
javadoc output:
error: module-info.class not allowed on patch path: /usr/**redacted**/jdk/src/jdk9/jdk/src/java.base/share/classes/module-info.java
- backported by
-
JDK-8177590 module-info on patch path should not produce an error
-
- Resolved
-
- blocks
-
JDK-8175346 javadoc does not handle Locations correctly with --patch-module
-
- Closed
-
- duplicates
-
JDK-8175505 javac emits "error module-info not allowed on patch path"
-
- Closed
-
- relates to
-
JDK-8176743 tools/javac/modules/MOptionTest.java test fails on Mac
-
- Closed
-
-
JDK-8176777 Add tools/javac/modules/MOptionTest.java test to the problem list
-
- Closed
-