RFR: 8350443: GHA: Split static-libs-bundles into a separate job [v4]

[Jiangli Zhou]

On Wed, 26 Feb 2025 14:59:11 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> Yes, we should distinguish between `static-libs` and `static` JDK. Currently, we refer `static` JDK as a 'fully' statically linked `java` launcher, plus `lib/modules` and other JDK resource files needed for runtime. 
>> 
>> For longer term, including `static-libs-bundles` by default may be what we want. For example, in our current hermetic Java prototype, we release a regular JDK + static-libs. The final hermetic Java image creation step builds the single image using:
>> 
>> - launcher (code)
>> - JDK/hostpot `static-libs`
>> - lib/modules
>> - JDK resource files
>> - application classes and resources
>> - application natives and dependencies
>> 
>> During the image creation process, a launcher executable is linked using the launcher `.o` file, (needed) JDK/hotspot static libs, application natives and dependencies (in `.o` files or static libraries).
>
> Great! Let's integrate and unblock @jianglizhou's work.

Thank you, @shipilev!

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

PR Comment: https://git.openjdk.org/jdk/pull/23715#issuecomment-2685854569