JDK-8160641 : PostProcessingPlugin and ExecutableImage should not be part of plugin API
- Type: Sub-task
- Component: tools
- Sub-Component: jlink
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-06-30
- Updated: 2016-07-07
- Resolved: 2016-06-30
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 b126Fixed  |
Description
All built-in plugins are TransformerPlugins. PostProcessingPlugin was supposed to be used by verifiers, processors etc. But there are not PostProcessorPlugins in internal plugins. Just like ResourcePrevisitor, PostProcessor could just be an internal interface for now. If we want to revisit Post processing plugins in future, we could add to (experimental) jlink API. TransformerPlugin being the only remaining Plugin type, the visit method of TransformerPlugin can be moved to Plugin. And TransformerPlugin can be removed.