JDK-6999210 : javac should be able to warn of anomalous conditions in classfiles
- Type: Enhancement
- Component: tools
- Sub-Component: javac
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic,linux
- CPU: generic,x86
- Submitted: 2010-11-11
- Updated: 2017-05-16
- Resolved: 2011-03-08
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 7 |
|---|
7 b123Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
6966357 changed javac to only accept classfile attributes defined for the version of the containing class file. This has been seen as a problem/regression by some folk who have been using v49 attributes in v48 classfiles and expecting them to work. To cover this situation and any related issues that may arise, it is proposed to add a new -Xlint suboption to control all warnings that javac may generate related to anomalous conditions in the class files that it reads.
Comments
|