JDK-8257617 : TestLinkPlatform fails with new Java source version
- Type: Bug
- Component: tools
- Sub-Component: javadoc(tool)
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2020-12-02
- Updated: 2021-07-12
- Resolved: 2020-12-04
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 16 |
|---|
16 b28Fixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
Two tests in TestLinkPlatform use a properties file with custom platform documentation URLs. The file is part of the static text fixture and only contains entries for the currently supported versions. Therefore, whenever a new source version is added, it will not have a URL defined in the properties file, causing the tests to fail. The best solution seems to create the file dynamically with entries for all known versions.
Comments
|