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
...and please don’t forget the packager services! Perhaps it could be made
available as a maven module?
/Lennart Börjeson
Electrogramma ab iPhono meo missum est
> 7 aug. 2018 kl. 19:54 skrev Kevin Rushforth :
>
> We're still aiming for that, although it might be a bit after JDK 11 ships.
>
We're still aiming for that, although it might be a bit after JDK 11 ships.
-- Kevin
On 8/7/2018 10:02 AM, Michael Paus wrote:
I don't know whether the following statement is still valid, but if it
is,
then it may not be worth the effort to resurrect the old javapackager
if at least an EA
I don't know whether the following statement is still valid, but if it is,
then it may not be worth the effort to resurrect the old javapackager
if at least an EA build of the new one is so close.
On 6/27/2018 3:30 PM, Kevin Rushforth wrote:
/We're aiming to get this into JDK 12 early enough so
Someone could certainly do that.
We think there is enough interest in having a standard tool that it is
worth spending effort on a replacement tool that will be part of
standard JDK builds, including OpenJDK builds that have never had
javapackager. In the mean time, if a standalone build of
The motivation for a new packager states a need for a a packager, but
not why the javapackager can't continue.
With all the work that went into javapackager, why can't it simple be
released for continued development outside Oracle, if they don't want to
maintain it.
The javapackager has worked
Well, while I can surely use the packager from JDK 10 and bundle my application
with 11, I'd still miss out on the packager service, i.e. the application would
not be able to use the UserJvmOptions.
It seems to me the packager service has been completely forgotten? JDK-8200758
does not mention
Hi Lennart,
You should be able to use the packager from JDK 10, see
https://bugs.openjdk.java.net/browse/JDK-8203379.
There is a draft for a replacement, see
https://bugs.openjdk.java.net/browse/JDK-8200758.
- Nir
On Tue, Aug 7, 2018 at 12:28 PM, Lennart Börjeson
wrote:
> I'm migrating to
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]
http://mail.openjdk.java.net/pipermail/core-libs-dev/2018-May/053503.html
[3]
I'm migrating to JDK 11 and OpenJFX 11, and would like to continue using the
packager and the associated packager service (i.e. the UserJvmOptions).
AFAIK, those are gone from the available binary builds, but still there in the
code. Is there a way to use them without resorting to build openjfx
14 matches
Mail list logo
