jdk-14-jpackage+1-33 on jdk.java.net

Scott Palmer swpalmer at gmail.com
Tue Aug 27 14:59:21 UTC 2019

Unless you added the --win-console option, I think this is expected.  Windows has a rather silly concept of console vs. window applications.  To avoid a console window popping up when you don’t expected it, the default launcher is in ‘window’ mode, not ‘console’ mode.

You need to know which kind of windows application you are building. Command line tools like javac would need to be packaged with the --win-console option.


> On Aug 27, 2019, at 4:06 AM, Schnoor Jonas <Schnoor.Jonas at scheidt-bachmann-st.de> wrote:
> First of all: Thank you very much for JPackage. This looks very promising.
> To give some feedback: I just tried JPackage on Windows 10 and I believe I ran into this bug: https://bugs.openjdk.java.net/browse/JDK-8211299
> It says the bug is fixed but I do not see anything written to either System.out or System.err.
> To make sure it was not something I am doing inside my application I tested it with a simple "Hello World" example and got the same result.
> When executing the JAR file directly using java -jar <JAR-File> I get the expected output in the CMD window.
> Can someone confirm this? Is this expected behaviour?
> BTW: When running the application inside the Git Bash (with MinGW) the output is displayed. But inside a Powershell/CMD window the output is _not_ displayed.
> If the application is started from a batch file no output is displayed either.
> -- Jonas

More information about the core-libs-dev mailing list