Forward a copy of this to the port list as well if of any interest.
My understanding is that the support list for javapackager though is
openjfx-dev. My further understanding is that javapackager represents the
on-going support of appbundler. It does code signing, builds application dmg’s,
package installers, etc.
I am trying to embed a Java 9 JDK into my application based off of javapackager
builds.
It appears you have to manually replace the default embedded JDK (8 for me)
with the Java 9 one. How this is added seems a little different from how I
remember appbundler applications but I didn’t do a lot with embedded
previously. For the Java 9 early access having an embedded test version for the
application seemed like a good idea.
I got a small test app to work but the full application is currently as shown
below.
Michael Hall
Begin forwarded message:
> From: Michael Hall <mik3h...@gmail.com>
> Subject: Re: javapackager
> Date: April 11, 2015 at 3:48:21 PM CDT
> To: Danno Ferrin <danno.fer...@oracle.com>
>
> On Apr 9, 2015, at 6:53 PM, Michael Hall <mik3h...@gmail.com> wrote:
>
>> On Apr 9, 2015, at 6:19 PM, Michael Hall <mik3h...@gmail.com> wrote:
>>
>>> I was just going to add java version to the JFrame title to make sure this
>>> is working right but it seems to be.
>>
>> Still 1.8 for some reason. But differences in the jdk layout are as you
>> suggested probably the reason.
>>
>
> Not sure if you still want to leave this off-list.
> I got my small test application working with Java 9.
> I am still having problems with the full application I’m trying to test.
> The error seems to be…
>
> ./HalfPipe9.app/Contents/MacOS/HalfPipe9
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at us.hall.osx.OSXApplication.<init>(OSXApplication.java:31)
> at us.hall.osx.OSXApplication.getApplication(OSXApplication.java:118)
> at us.hall.hp.common.LoaderLaunchStub.<clinit>(LoaderLaunchStub.java:35)
> Caused by: java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission" "canProcessApplicationEvents")
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:468)
> at
> java.security.AccessController.checkPermission(AccessController.java:894)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:541)
> at com.apple.eawt.Application.checkSecurity(Application.java:73)
> at com.apple.eawt.Application.<clinit>(Application.java:61)
> ... 3 more
> 2015-04-11 14:44:50.148 HalfPipe9[3528:1403] .:Failed to launch JVM
>
> The .:Failed to launch JVM is all that shows up in console so I tried
> launching the app itself command line.
>
> The normal works when launched this way.
> The Info.plist includes…
>
> -Djava.security.manager
> -Djava.security.policy=$APP_ROOT/Contents/JavaApp/all.policy
>
> I’m not sure if your version of the launcher supports the same env variable
> type settings like $APP_ROOT?
> I notice the JVMRuntime property is set to…
> $APPDIR/plugins/Java
> I’m not familiar with $APPDIR, would that be <the.app>/Contents? plugins
> should be Plugins shouldn’t it, a little surprised thats not case sensitive.
>
> Michael Hall
>
>
>
>
>
