JDK-8076646 : nashorn tests should avoid using package names used by nashorn sources
- Type: Bug
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-04-03
- Updated: 2015-09-29
- Resolved: 2015-04-03
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 8 | JDK 9 |
|---|---|
8u60Fixed  |
9 b59Fixed |
Related Reports
|
Relates :
|
Description
Many test package names are same as nashorn source package names (eg. jdk.nashorn.api.scripting, jdk.nashorn.internal.runtime). It is better to avoid this:
1) We don't have any package-private access from tests to nashorn internal, package-private classes
2) Even though same package name is used, nashorn is loaded by boot loader or extension loader (depending on jdk version) and tests are loaded by launcher loader and so these are different runtime packages anyway. Any confusion within IDE ("same package " as seen in IDE) can be avoided by different package names.
3) In a modular (jigsaw) world, we need to avoid this package name collision b/w source and test classes.