> On Feb 22, 2020, at 12:04 PM, Michael Hall <mik3h...@gmail.com> wrote:
>
>
>
>> On Feb 22, 2020, at 11:10 AM, Michael Hall <mik3h...@gmail.com
>> <mailto:mik3h...@gmail.com>> wrote:
>>
>>
>>
>>> On Feb 22, 2020, at 10:14 AM, Tom Schindl <tom.schi...@bestsolution.at
>>> <mailto:tom.schi...@bestsolution.at>> wrote:
>>>
>>> At Eclipse it is tracked as
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559482
>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=559482>
>> Thanks.
>> Not quite sure what would of triggered it yesterday.
>>
>
> OK. So I think what the deal was is that the jpackage development branch,
> that I’ve been using for some time, dodged the bullet on this bug. It picked
> it up when it merged in with the main stream. And I picked it up when I
> installed that.
>
> Unfortunately I didn’t save a prior jdk14 jpackage jre. So to launch Eclipse
> I had to remove all JDK 14 JRE’s. Then Eclipse wanted a jdk14. So I renamed
> an old jdk13 jpackage one to jdk14. Eclipse than launched.
> To make this a little easier to work with I changed the default installed jre
> to jdk-13, the eclipse.ini vm to jdk-13 and renamed the jpackage one back to
> jdk-13.jdk.
> I think now I should be able to re-install a jdk14 to test that and current
> jpackage. Just for now eclipse will use a slightly older, jpackage specific,
> one.
>
My current understanding is this. Including native commands with an OS X
application with an embedded JRE does not work at all for current
applications/JRE’s.
I’m not sure what the application problem with jlink was last night but it is
working tonight. From the earlier problems with Eclipse I still had jdk14
removed from JavaVirtualMachines. The version command started indicating jdk13.
I put 14 back in and built a current jpackage application with a jlink commands
included runtime.
I then again removed jdk14 from JavaVirtualMachines.
exec java -version
openjdk version "13-internal" 2019-09-17
OpenJDK Runtime Environment (build 13-internal+0-jdk13-jpackage.49)
OpenJDK 64-Bit Server VM (build 13-internal+0-jdk13-jpackage.49, mixed mode,
sharing)
versions
System.in:3:java.version=14
System.in:5:java.version.date=2020-03-17
System.in:15:java.class.version=58.0
System.in:16:java.vm.specification.version=14
System.in:19:java.vm.version=14+36-1461
System.in:22:java.runtime.version=14+36-1461
System.in:25:java.specification.version=14
It only finds the command in the JavaVirtualMachines 13 runtime. Not the
application included 14 one.
It only works if the OS has a correct link in place
exec which java
/usr/bin/java
exec ls -l /usr/bin/java
lrwxr-xr-x 1 root wheel 74 Mar 19 2019 /usr/bin/java ->
/System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java
It does not work for jlink or jpackage because no such link exists.
Currently, at least for Runtime exec including the commands with the
application does no good.
