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

2025-04-11 Thread Christoph Langer
On Sat, 5 Apr 2025 04:49:03 GMT, Christoph Langer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains four additional >> c

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

2025-04-10 Thread Severin Gehwolf
On Sat, 5 Apr 2025 04:49:03 GMT, Christoph Langer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains four additional >> c

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

2025-04-07 Thread Severin Gehwolf
On Sat, 5 Apr 2025 04:45:00 GMT, Christoph Langer wrote: >> Severin Gehwolf has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains four additional >> c

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

2025-04-07 Thread Severin Gehwolf
On Sat, 5 Apr 2025 04:49:03 GMT, Christoph Langer wrote: > I see that you're actively on the upgradeable files. What about #24190? Let's keep the discussion on #24190, please. - PR Comment: https://git.openjdk.org/jdk/pull/24388#issuecomment-2782507174

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

2025-04-04 Thread Christoph Langer
On Fri, 4 Apr 2025 15:22:10 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 [v2]

2025-04-04 Thread Severin Gehwolf
On Fri, 4 Apr 2025 15:22:10 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 [v2]

2025-04-04 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