Hi Kevin,
Aha! That explains it, and yes, adding that flag fixes the issue. Thanks!
The only documentation i have seen is this:
https://openjdk.java.net/jeps/343
And while that does mention this flag, the mention is deep in the section
describing all the flags, which i have to confess i did
Hi Alexey,
Here is a demo project:
https://github.com/tomwhoiscontrary/jpackage-demo
If i run this on Windows (Windows 10 in a VM), it produces this output:
https://gist.github.com/tomwhoiscontrary/ee33dda3c124d8a67bd5bba5b8d5e32d
Which includes the following command line:
You need to run jpackage the "--win-console" option in order to get a
console app. This is intentional and documented.
-- Kevin
On 5/2/2019 9:19 AM, Alexey Semenyuk wrote:
Hi Tom,
Thank for providing a reference to the demo project and build output.
In your example you use jpackage to
Hi Tom,
Thank for providing a reference to the demo project and build output.
In your example you use jpackage to produce an application image, not an
exe or msi installers. Just to be clear on the test scenario.
Test app prints "Hello, world!" to stdout as far as I can tell from
When you say "doesn't do anything when run", do you perhaps mean that
you have some print statements in your program and you don't see them
when you run it from a command shell? If so, then this is expected, and
you need to add the "--win-console" option.
If it's something else, then Alexey's
Hi Tom,
What is your jpackage command line? Could you please rerun it with
JPACKAGE_DEBUG environment variable set to "true".
- Alexey
On 4/30/2019 11:15 AM, Tom Anderson wrote:
Hello,
I am trying out the early-access jpackage tool. It works perfectly on
Linux, but on Windows produces a
Hello,
I am trying out the early-access jpackage tool. It works perfectly on
Linux, but on Windows produces a binary which does not do anything when
run.
I would like to either fix any error i have made, or help you identify a
bug, if there is one!
Is this the right place to come with
