JDK-8074071 : Sjavac reports a deprecation error where javac doesn't
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Not an Issue
- Submitted: 2015-03-01
- Updated: 2015-06-10
- Resolved: 2015-06-10
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 9 |
|---|
9Resolved  |
Related Reports
|
Blocks :
|
Description
Sjavac outputs errors such as the following: warning: [deprecation] XYZ in some.package has been deprecated import static some.package.SomeEnum.INVALID_PERIOD; while invoking javac directly doesn't. The strange part is that this error comes from javac, so there seems to be some difference between invoking javac through the API and through the command line.
Comments
|