> On Jan 15, 2019, at 6:55 PM, Scott Palmer wrote:
>
>
> You are explicitly invoking commands of that JDK. What would you expect if
> you ran ‘~/Documents/jdk-13.jdk/Contents/home/bin/java’ ?
You are explicitly invoking a binary executable. I would of expected it to try
and run against wh
> On Jan 15, 2019, at 11:43 AM, Michael Hall wrote:
>> On Jan 15, 2019, at 10:35 AM, Andy Herrick wrote:
>> On 1/15/2019 11:25 AM, Michael Hall wrote:
On Jan 15, 2019, at 10:19 AM, Andy Herrick wrote:
On 1/15/2019 11:04 AM, Michael Hall wrote:
> java -version
> openjdk
> On Jan 15, 2019, at 12:48 PM, Rachel Greenham
> wrote:
>
> On 15/01/2019 17:36, Michael Hall wrote:
>>> On Jan 15, 2019, at 10:55 AM, Rachel Greenham
>>> wrote:
>>>
>>> My understanding was that this particular jdk build only exists for the
>>> sake of getting jpackage out there into our
On 15/01/2019 17:36, Michael Hall wrote:
On Jan 15, 2019, at 10:55 AM, Rachel Greenham wrote:
My understanding was that this particular jdk build only exists for the sake of
getting jpackage out there into our hands (hence my point about putting it out
as a jlinked app instead),
True, which
> On Jan 15, 2019, at 10:55 AM, Rachel Greenham
> wrote:
>
> My understanding was that this particular jdk build only exists for the sake
> of getting jpackage out there into our hands (hence my point about putting it
> out as a jlinked app instead),
True, which is a little different in and
My understanding was that this particular jdk build only exists for the
sake of getting jpackage out there into our hands (hence my point about
putting it out as a jlinked app instead), and if you want to play with
jdk13-ea in its own right, should probably get a fresh one to do just
that, as t
> On Jan 15, 2019, at 10:35 AM, Andy Herrick wrote:
>
>
> On 1/15/2019 11:25 AM, Michael Hall wrote:
>>> On Jan 15, 2019, at 10:19 AM, Andy Herrick wrote:
>>>
>>>
>>> On 1/15/2019 11:04 AM, Michael Hall wrote:
java -version
openjdk version "12-internal" 2019-03-19
OpenJDK Run
On 1/15/2019 11:25 AM, Michael Hall wrote:
On Jan 15, 2019, at 10:19 AM, Andy Herrick wrote:
On 1/15/2019 11:04 AM, Michael Hall wrote:
java -version
openjdk version "12-internal" 2019-03-19
OpenJDK Runtime Environment (build 12-internal+0-jdk12-jpackage.7)
OpenJDK 64-Bit Server VM (build 1
> On Jan 15, 2019, at 10:25 AM, Rachel Greenham
> wrote:
>
> ... simply that you don't *want* jpackage's jdk to be in your path, you don't
> want it to be the default, you *only* want it to run jpackage *itself*, in
> create-image using --runtime-image pointing to your already jlinked runtim
> On Jan 15, 2019, at 10:19 AM, Andy Herrick wrote:
>
>
> On 1/15/2019 11:04 AM, Michael Hall wrote:
>> java -version
>> openjdk version "12-internal" 2019-03-19
>> OpenJDK Runtime Environment (build 12-internal+0-jdk12-jpackage.7)
>> OpenJDK 64-Bit Server VM (build 12-internal+0-jdk12-jpackag
... simply that you don't *want* jpackage's jdk to be in your path, you
don't want it to be the default, you *only* want it to run jpackage
*itself*, in create-image using --runtime-image pointing to your already
jlinked runtime image using your usual JDK; then in create-installer,
using --app-
On 1/15/2019 11:04 AM, Michael Hall wrote:
java -version
openjdk version "12-internal" 2019-03-19
OpenJDK Runtime Environment (build 12-internal+0-jdk12-jpackage.7)
OpenJDK 64-Bit Server VM (build 12-internal+0-jdk12-jpackage.7, mixed mode,
sharing)
This is the first jpackage EA build that w
> On Jan 15, 2019, at 9:18 AM, Rachel Greenham wrote:
>
> surely simpler just unpack the jpackage jdk into, say, /opt/jdk-13, ie:
> emphatically *not* installed as a JVM in /Library/Java/JavaVirtualMachines,
> and then it doesn't get in the way of anything else. When you want to use
> jpacka
surely simpler just unpack the jpackage jdk into, say, /opt/jdk-13, ie:
emphatically *not* installed as a JVM in
/Library/Java/JavaVirtualMachines, and then it doesn't get in the way of
anything else. When you want to use jpackage invoke, directly,
/opt/jdk-13/bin/jpackage, which is a path you
I am running High Sierra too (10.13.3), and don't see this error with a
simple test app. can you share with me the command options used, also if
you specify --resource-dir what is in the directory pointed to ?
/Andy
On 1/15/2019 9:23 AM, Kustaa Nyholm wrote:
On 15 Jan 2019, at 16.11, Andy H
> On 15 Jan 2019, at 16.11, Andy Herrick wrote:
>
> You can do this all in one step "${PACKAGER} create-installer dmg "
Thank you for you help, I appreciate it.
I tested above and it fails with what looks suspiciously same error I was
experiencing with
javapackager and jpackager, see below
On 1/15/2019 12:08 AM, Kustaa Nyholm wrote:
Seems to work not! Thanks!
Some small quibbles:
The build directory is not kept or used:
Using default package resource Runtime-Info.plist.template [Java Runtime
Info.plist] (add Runtime-Info.plist to the resource-dir to customize)
Kept working d
> On 15 Jan 2019, at 12.57, Michael Hall wrote:
>
> Usually the latest jdk with the command would be the one you’d want?
Funnily enough, I wanted to quickly test something (jdeps) from the command
line,
and sure enough it evoked jdk-13 ea which is NOT what I want cause my main goal
is to mov
> On Jan 14, 2019, at 11:50 PM, Kustaa Nyholm
> wrote:
>
>
>
>> On 15 Jan 2019, at 7.36, Michael Hall wrote:
>>
>> FWIW, for OS X I just set this in my .bash_profile
>
> Thanks, my preference is to be explicit so that my build don't depend on the
> environment
> and changes to it , I've
> On 15 Jan 2019, at 7.36, Michael Hall wrote:
>
> FWIW, for OS X I just set this in my .bash_profile
Thanks, my preference is to be explicit so that my build don't depend on the
environment
and changes to it , I've got about 8 x jdk on this machine and I (almost) never
use the command
lin
> On Jan 14, 2019, at 11:08 PM, Kustaa Nyholm
> wrote:
>
>
> For reference and posterity in case anyone comes hear searching for a worked
> out sample here is my simplistic test script:
>
> #!/bin/bash
>
> set -e
>
> PACKAGER=/Library/Java/JavaVirtualMachines/jdk-13.jdk/Contents/Home/bin/
Seems to work not! Thanks!
Some small quibbles:
The build directory is not kept or used:
Using default package resource Runtime-Info.plist.template [Java Runtime
Info.plist] (add Runtime-Info.plist to the resource-dir to customize)
Kept working directory for debug: /Users/nyholku/EazyCNC-Proje
On 1/14/2019 9:02 AM, Kustaa Nyholm wrote:
Thanks!
I could have sworn I had the correct jpackage in use, turns out I using
referring to jpackager.
When I tried jpackage (copied jpackage from 13 to my 11 jdk) I got:
dyld: Library not loaded: @rpath/libjli.dylib
Referenced from:
/Librar
Thanks!
I could have sworn I had the correct jpackage in use, turns out I using
referring to jpackager.
When I tried jpackage (copied jpackage from 13 to my 11 jdk) I got:
dyld: Library not loaded: @rpath/libjli.dylib
Referenced from:
/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Conten
I can see from the verbose message that you are not using the jpackage
from the latest EA2 at https://jdk.java.net/jpackage/
(run jpackage --version to see what version you are running)
Did you download the earlier EA and copy it over installed jdk-11.0.1 ?
In any case the behavior you are try
Hi,
over the weekend I tried to use the EA jpackage from here:
https://jdk.java.net/jpackage/
I invoke it like this:
PACKAGER=/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/jpackager
${PACKAGER} \
create-image \
--build-root build-jpackager \
--verbose \
--echo-mode \
--add
26 matches
Mail list logo
