JDK-8175057 : module-info on patch path should not produce an error
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2017-02-16
- Updated: 2017-03-25
- Resolved: 2017-03-14
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 10 | JDK 9 |
|---|---|
10Fixed  |
9 b162Fixed |
Related Reports
|
Blocks :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
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
Comments
|