Re: RFR: 8353185: Introduce the concept of upgradeable files in context of JEP 493 [v5]

2025-04-11 Thread Christoph Langer
On Wed, 9 Apr 2025 16:10:20 GMT, Severin Gehwolf wrote: >> For JEP 493-enabled builds there are no JMODs. Certain files come from the >> installed JDK image when a user creates a custom run-time from it. This is >> problematic for example for files that often come from a different package >> (

Re: RFR: 8353185: Introduce the concept of upgradeable files in context of JEP 493 [v5]

2025-04-10 Thread Severin Gehwolf
> For JEP 493-enabled builds there are no JMODs. Certain files come from the > installed JDK image when a user creates a custom run-time from it. This is > problematic for example for files that often come from a different package > (e.g. `cacerts` file for Linux distro builds of OpenJDK package

Re: RFR: 8353185: Introduce the concept of upgradeable files in context of JEP 493 [v5]

2025-04-10 Thread Alan Bateman
On Wed, 9 Apr 2025 16:10:20 GMT, Severin Gehwolf wrote: >> For JEP 493-enabled builds there are no JMODs. Certain files come from the >> installed JDK image when a user creates a custom run-time from it. This is >> problematic for example for files that often come from a different package >> (

Re: RFR: 8353185: Introduce the concept of upgradeable files in context of JEP 493 [v5]

2025-04-09 Thread Magnus Ihse Bursie
On Wed, 9 Apr 2025 16:10:20 GMT, Severin Gehwolf wrote: >> For JEP 493-enabled builds there are no JMODs. Certain files come from the >> installed JDK image when a user creates a custom run-time from it. This is >> problematic for example for files that often come from a different package >> (