RFR: 8311302: Allow for jlinking a custom runtime without packaged modules being present [v23]

[Severin Gehwolf]

On Wed, 3 Apr 2024 22:31:39 GMT, Mandy Chung <mchung at openjdk.org> wrote:

>> Severin Gehwolf has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   Move CreateLinkableRuntimePlugin to build folder
>>   
>>   Keep runtime link supporting classes in package
>>   jdk.tools.jlink.internal.runtimelink
>
> Thanks for the investigation w.r.t. extending jimage.  It does not seem worth the effort in pursuing the support of adding resources to an existing jimage file.   To me, putting the diff data under `lib` directory as a private file is a simpler and acceptable solution.   It allows the second jlink invocation to avoid the plugin pipeline if the per-module metadata is generated in normal jlink invocation.
> 
> (An observation: The current implementation requires the diffs to be generated as a plugin.  For this approach, it may be possible to implement with a separate main class that calls JLink API and generates the diffs.)

@mlchung @AlanBateman Any thoughts on this latest version? Is this going into the direction you had envisioned? Any more blockers? The CSR should be up-to-date and is open for review as well. If no more blockers I'll go over this patch once more and clean it up to prepare for integration. Thanks!

-------------

PR Comment: https://git.openjdk.org/jdk/pull/14787#issuecomment-2044593102