On Fri, 27 Jun 2025 16:15:57 GMT, Magnus Ihse Bursie wrote:
>> In the static JDK image, a single humongous java executable is generated,
>> and no other launcher, such as javac. This makes it impossible to run our
>> jtreg tests, which assume these are present.
>>
>> The solution is fortunatel
On Fri, 27 Jun 2025 16:15:57 GMT, Magnus Ihse Bursie wrote:
>> In the static JDK image, a single humongous java executable is generated,
>> and no other launcher, such as javac. This makes it impossible to run our
>> jtreg tests, which assume these are present.
>>
>> The solution is fortunatel
> In the static JDK image, a single humongous java executable is generated, and
> no other launcher, such as javac. This makes it impossible to run our jtreg
> tests, which assume these are present.
>
> The solution is fortunately simply: we just need to add a bunch of trivial
> launchers, whic
On Thu, 3 Apr 2025 14:09:58 GMT, Alan Bateman wrote:
> Right now, the static-jdk image is a bit strange in that it's a modular
> run-time image but with all native code compiled into bin/java. In time we
> hope that jlink will be able to create a static image where everything is in
> the singl
On Thu, 3 Apr 2025 14:24:18 GMT, Magnus Ihse Bursie wrote:
> So while we continue to hammer out how to improve this, I think it is
> important to be able to test static builds in mainline, or they will break.
Agree with @magicus on the importance of being able to test static builds in
mainlin
On Thu, 3 Apr 2025 14:09:58 GMT, Alan Bateman wrote:
> As regards the shim when I wonder if it should use CreateProcessW but maybe
> it doesn't matter for the test environments where they will run.
I must admit that I am not very well versed in Windows programming. What is the
difference? I th
On Wed, 2 Apr 2025 14:54:35 GMT, Magnus Ihse Bursie wrote:
> In the static JDK image, a single humongous java executable is generated, and
> no other launcher, such as javac. This makes it impossible to run our jtreg
> tests, which assume these are present.
>
> The solution is fortunately simp
On Wed, 2 Apr 2025 14:54:35 GMT, Magnus Ihse Bursie wrote:
> In the static JDK image, a single humongous java executable is generated, and
> no other launcher, such as javac. This makes it impossible to run our jtreg
> tests, which assume these are present.
>
> The solution is fortunately simp
> In the static JDK image, a single humongous java executable is generated, and
> no other launcher, such as javac. This makes it impossible to run our jtreg
> tests, which assume these are present.
>
> The solution is fortunately simply: we just need to add a bunch of trivial
> launchers, whic
On Wed, 2 Apr 2025 14:54:35 GMT, Magnus Ihse Bursie wrote:
> In the static JDK image, a single humongous java executable is generated, and
> no other launcher, such as javac. This makes it impossible to run our jtreg
> tests, which assume these are present.
>
> The solution is fortunately simp
In the static JDK image, a single humongous java executable is generated, and
no other launcher, such as javac. This makes it impossible to run our jtreg
tests, which assume these are present.
The solution is fortunately simply: we just need to add a bunch of trivial
launchers, which are thin w
11 matches
Mail list logo
