JDK-8162538 : plugin API should avoid read only pool, have module view separated from resource view and have pool builder to modify
- Type: Sub-task
- Component: tools
- Sub-Component: jlink
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-07-26
- Updated: 2020-04-15
- Resolved: 2016-07-28
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 |
|---|
9 b130Fixed  |
Related Reports
|
Relates :
|
Description
Plugin API should use * Pool and Pool builder separated and avoid read-only pool concept * Pool entry view should be separated from module view * Should avoid bean style names * Should avoid ? extends Foo types as that does not add much value.