JDK-8147894 : Refresh jlink API
  • Type: Task
  • Component: tools
  • Sub-Component: jlink
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-01-21
  • Updated: 2016-09-08
  • Resolved: 2016-09-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.
JDK 9
9Fixed
Related Reports
Relates :  
JDK-8160063 - Provide a means to disable a plugin via the command line
Relates :  
JDK-8160359 - Improve jlink logging for cases when a plugin throws exception
Sub Tasks
JDK-8146721 :  
FileCopierPlugin should not create fake module - Resolved
JDK-8147472 :  
Jlink, ModuleDescriptor returned by Pool.Module doesn't reflect actual content of a module - Closed
JDK-8147491 :  
module graph consistency checks after jlink plugins operate on module pool - Resolved
JDK-8147794 :  
Jlink's ModuleEntry.stream can't be consumed more than once and ModuleEntry content should be read only if needed - Resolved
JDK-8147897 :  
Examine custom ImageBuilder support - Resolved
JDK-8160641 :  
PostProcessingPlugin and ExecutableImage should not be part of plugin API - Resolved
JDK-8161055 :  
Remove plugin ordering by isAfter, isBefore. - Resolved
JDK-8162538 :  
plugin API should avoid read only pool, have module view separated from resource view and have pool builder to modify - Resolved
JDK-8162782 :  
jlink ResourcePool.releaseProperties should be removed - Resolved
Description
This issue serves as the main task to track issues with jlink plugin API.
Comments
jdk.tools.jlink.internal.packager.AppRuntimeImageBuilder in a bridge between jdk.packager module and jlink. It shows the requirements from packager on jlink to create a custom image for an application. jdk.packager is located in the FX repo which is not built together with jdk and it adds significant complexity in coordinating any jlink API change that impacts the packager. This bridge is an interim solution until jdk.packager is moved to the jdk repo or the jlink API is refreshed and expected less frequent change. During the exercise of introducing this bridge, the usage of the jlink API from packager is significantly simplified. The packager creates a custom image of the given modulepaths, root modules and possibly limit mods. Packager itself strips off the native commands and excludes native debug symbols and some other files (i.e. invoke the builtin jlink plugins). Packager also provides a way to take jlink-plugin options from users and then pass to jlink. Since ModuleFinder only supports JMOD files at link time, packager needs the capability to get a module finder configured for jlink time so that they can read content from JMOD file, when appropriate.
14-06-2016