JDK-8161055 : Remove plugin ordering by isAfter, isBefore.
- Type: Sub-task
- Component: tools
- Sub-Component: jlink
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-07-08
- Updated: 2016-07-14
- Resolved: 2016-07-08
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 b127Fixed  |
Description
Currently there are two methods - isAfter, isBefore methods both returning Set<String>. These are used for plugin ordering. But, there are problems: 1) plugins are ordered based on category and then ordered by isAfter/isBefore within the category! 2) Plugins must know each-other by name to use this isAfter/isBefore method overrides [in addition to being plugins of same category]. We need some other solution for ordering (if at all!). For now, it is better to remove isAfter/isBefore to avoid API pollution. None of the internal plugins use that. There is only a specific test class that uses these to exercise the API!