If anyone wants to try to reproduce this, here is the Dockerfile I used to
create the Windows docker image
# escape=`
FROM mcr.microsoft.com/windows:1903 AS jdk17
# $ProgressPreference:
https://github.com/PowerShell/PowerShell/issues/2138#issuecomment-251261324
SHELL [ "powershell", "-Command",
Hi Sverre,
Interesting, I don't see changes in jpackage code related to the issue.
In particular jdk.jpackage.internal.IOUtils.writableOutputDir() function
is the same in JDK14, JDK17, and mainline.
- Alexey
On 2/18/2022 8:31 AM, Sverre Moe wrote:
I executed our JDK11 docker image, which
I executed our JDK11 docker image, which works fine with JDK11 and JDK14
(for jpackage support).
Then I installed the JDK17 MSI package, changed JAVA_HOME and PATH.
Building our application now with JDK17 it still cannot write to the
"build/native" jpackage output directory.
Leads me to conclude
I ran cacls after the failed jpackage.
C:\temp\my-javafx-application>cacls build
C:\temp\my-javafx-application\build F
CREATOR OWNER:(OI)(CI)(IO)F
R
CREATOR GROUP:(OI)(CI)(IO)R
On 05/10/2021 08:54, Sverre Moe wrote:
With JDK 17, jpackage fails to write to the destination directory on
Windows.
It worked fine with JDK 11 (with jpackage from JDK14) and Docker.
Only happens on Windows docker. Running directly on WIndows it works with
JDK 17.
What has changed with
With JDK 17, jpackage fails to write to the destination directory on
Windows.
It worked fine with JDK 11 (with jpackage from JDK14) and Docker.
Only happens on Windows docker. Running directly on WIndows it works with
JDK 17.
What has changed with jpackage that it no longer can write to the
