Why static_jli for java/javaw on Windows?

Erik Joelsson erik.joelsson at oracle.com
Thu Sep 13 23:17:03 UTC 2018

I checked and the copying of java.exe was done in the now legacy jre 
installer, so from what I can tell, there is no longer a need for static 


On 2018-09-13 09:14, Erik Joelsson wrote:
> Hello,
> Reading that bug, it seems the problem is when the installer copies 
> java.exe into the Windows system directory. In that case, it may not 
> have access to the msvcr re-distributables. I will try to find out if 
> our installers are still doing this.
> /Erik
> On 2018-09-13 06:32, Alan Bateman wrote:
>> On 13/09/2018 14:07, Magnus Ihse Bursie wrote:
>>> :
>>> Apparently, someone was trying to get rid of dll dependencies from 
>>> java.exe. Why that would be desirable it does not say. Neither why 
>>> this should not apply to all other launchers. (Perhaps there were 
>>> not that many in these days?)
>>> Do anyone think this still seems relevant? Otherwise I'd like to get 
>>> rid of this hack, and link java and javaw just like all the other 
>>> launchers.
>> I don't know if it is still needed but it seems to be related to the 
>> upgrade to VC 7 and an issue related to redistribution issue of the 
>> MS runtime. JDK-6282039 and JDK-6382014 have some info on this.
>> -Alan.

More information about the core-libs-dev mailing list