Right, that's a good idea. Thanks.
On Thu, Aug 9, 2018 at 3:32 PM Steve Hruda wrote:
> Johan,
> another temporary fix could be the META-INF attribute
> "Automatic-Module-Name". E.g. set it at the empty jar to
> javafx.controls.workaround
>
Johan,
another temporary fix could be the META-INF attribute
"Automatic-Module-Name". E.g. set it at the empty jar to
javafx.controls.workaround
https://docs.oracle.com/javase/10/docs/specs/jar/jar.html#main-attributes
Regards,
Steve
Am Sa., 14. Juli 2018 um 12:16 Uhr schrieb Steve Hruda <
We (Gluon) are looking into creating a JavaFX 11 version of the packager.
- Johan
On Thu, Aug 9, 2018 at 1:42 PM Cyril F wrote:
> I am sure the new jpackager tool will be a good substitute. But won't come
> before jdk12...
>
> In fact we are in the current situation :
> We have a
1. What forces you to make the switch from 8 to 11 at the same day when
jdk11 comes out?
2. The plan is that when jdk11 comes out there will already be an EA
version of jdk12 available which
already contains a version of the new packager which will also work
with jdk11 then.
As long as
I am sure the new jpackager tool will be a good substitute. But won't come
before jdk12...
In fact we are in the current situation :
We have a javaFX8 app distributed as a .exe with a bundled JRE.
We are mirating to javaFX11.
My fear is that there will be a gap between javafx11
See this message from Kevin Rushforth about a javapackager replacement:
We are proposing a JEP to add a new 'jpackager' tool [1] as a
> replacement for javapackager. The discussion is on core-libs-dev [2] [3]
> [4].
>
> -- Kevin
>
> [1] https://bugs.openjdk.java.net/browse/JDK-8200758
> [2]
>
I am following openjfx11 carefully, if I understand there won't be a packager
tool ? And the answer to this is to use the packager from the jdk10. If I also
understand the end of support of jdk10 start with the release of jdk11.
So how long will the not supported jdk10 packager will stay
