JDK-8164700 : (jdeprscan) update release and version logic in jdeprscan
- Type: Sub-task
- Component: tools
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- Submitted: 2016-08-24
- Updated: 2018-06-21
- Resolved: 2018-06-21
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 11 |
|---|
11Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Need to determine a mechanism for updating jdeprscan's supported -release values in lockstep with those of javac. If there is a compiler API that returns the supported versions, jdeprscan should use it. Otherwise, the following will need to be updated manually.
In Main.java:
final Set<String> releasesWithoutForRemoval = Set.of("6", "7", "8");
final Set<String> releasesWithForRemoval = Set.of("9");
The new release should be added to releasesWithForRemoval and the obsoleted release dropped from releasesWithoutForRemoval.
In LoadProc.java and TraverseProc.java, update @SupportedSourceVersion(RELEASE_9).
The resources/jdeprscan.properties file needs to be modified to update the usage message.
The readme.md file also needs to be updated. (But this is probably duplicate information from what's in the online reference manual documentation, so maybe this file should simply be removed.)
Comments
|