Quote:
Originally Posted by DNSB
After an update to Java 8 update 271 on Windows 10 x64, I started getting the same error as @Rand Brittain. The java path workaround fixed the issue. I did notice the Java path in the environment was still showing the old version's path.
|
I just installed that version, 8u271, and epubcheck still works for me.
On my system for some time now Oracle has been installing a Windows
symbolic hard link (?) to the current java version. In the System (not user) environment variables in the PATH environment variable it added
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
which is a
symbolic hard linked folder. The icon for that looks like a Windows shortcut but when you open its properties you don't get the usual properties window for a shortcut. I don't remember how I determined that it's a
symbolic hard link, which are rarely seen (in my experience) on Windows. (Hard links appear to be an obscure and not well publicized feature of NTFS. Allowing multiple named data streams in files is another one.)
So if you use that in your PATH you shouldn't need to keep updating your PATH when new versions are installed.
I installed the 64 bit version of Java and I'm guessing that the x86 in the above is something to make everyone happy, including x86 things.
I'm wondering why you guys aren't getting this slightly convoluted wrapper for the java path. Maybe if you had it with the explicit path the installer keeps using that and I got the new method when I rebuilt my system.
Edit: fix link type.