Den tor. 27. sep. 2018 kl. 00:49 skrev Kevin Rushforth <
kevin.rushfo...@oracle.com>:
> No, jlink won't link in a non-modular application. So the steps are:
>
> 1) Run jlink to create a Java runtime image, possibly stripped down, and
> include the javafx.* modules you need
> 2) Run jpackager to pa
+1 with the additional refactoring done.
Regards
Prasanta
On 25-Sep-18 6:03 PM, Kevin Rushforth wrote:
Yes, that seems like a good bit of additional cleanup. I'll do that.
-- Kevin
On 9/25/2018 1:41 AM, Prasanta Sadhukhan wrote:
Hi Kevin,
Removal looks ok but one thing, do we still need to
On https://openjfx.io/openjfx-docs/ I don't see any content, just
buttons and links that don't seem to do anything. Tried both Firefox and
Chrome. Is it just me?
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
Works for me on Vivaldi.
On Thu, Sep 27, 2018 at 5:39 PM Glenn Holmer wrote:
> On https://openjfx.io/openjfx-docs/ I don't see any content, just
> buttons and links that don't seem to do anything. Tried both Firefox and
> Chrome. Is it just me?
>
> --
> Glenn Holmer (Linux registered user #16682
Glenn Holmer wrote:
On https://openjfx.io/openjfx-docs/ I don't see any content, just
buttons and links that don't seem to do anything. Tried both Firefox and
Chrome. Is it just me?
Works for me on SeaMonkey.
Regards,
Joe1962
Without the reliance on javafx-swing I was able to create an image, package
and execute my test application.
Is the Swing problem a known bug in JavaFX 11?
The jlink runtime image I reckon now also contains the JavaFX modules?
Seems unnecessary when they already are dependencies.
/Sverre
Den tor
I missed seeing the swing exception in your earlier message. Yes, the
Swing issue is a known problem in openjfx11, JDK-8210759 [1], and is
documented in the release notes [2].
It will be fixed in openjfx12 just as soon as I push the fix for
JDK-8210092 [3] later today (the review was just fini
Any chance of getting the fix for JDK-8210759 backported to JDK 11? I
remember reading the OpenJDK will be patched up to 2023 (while Oracle JDK
will be patched up to 2026).
We deliver software that our customers could be running for a decade or
more. The LTS is the version we will then target when
You mean openjfx11, not JDK 11, right? Backporting this fix would mean
an openjfx 11.x update release would stop building or running with JDK
10. Not something that would be done lightly, since it would break the
"FX N runs with JDK N-1" policy we have been discussing lately. There is
an easy w
Den tor. 27. sep. 2018 kl. 18:50 skrev Kevin Rushforth <
kevin.rushfo...@oracle.com>:
> You mean openjfx11, not JDK 11, right? Backporting this fix would mean an
> openjfx 11.x update release would stop building or running with JDK 10. Not
> something that would be done lightly, since it would bre
On tor. 27. sep. 2018 kl. 18:18 wrote Kevin Rushforth <
kevin.rushfo...@oracle.com>:
>
> I missed seeing the swing exception in your earlier message. Yes, the
Swing issue is a known problem in openjfx11, JDK-8210759 [1], and is
documented in the release notes [2].
>
> It will be fixed in openjfx12
>
> How can we continue to upgrade to newer OpenJFX as time goes by. Will the
> later OpenJFX 13+ work with JDK 11 or is it just "FX N run JDK N-1" (one
> version backward support)?
>
There is a separate thread about this:
http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-September/022527.ht
This was discussed on the list earlier this week, and the current
proposal is to support OpenJFX N on JDK N-1 or later [1].
As part of a follow-on discussion, it was suggested that we might avoid
eagerly breaking JDK N-2 unless/until there is something we need from
JDK N-1 that makes breaking
Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos :
> We would probably target the Java 11 because it is LTS. Changes to JDK will
>> be backported up to september 2023 by the community. If we are interested
>> in getting updates on OpenJFX also we would then need to always upgrade
>> it.
>> I recko
On 2018-09-27 Sverre Moe wrote:
> Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos :
>
> > > We would probably target the Java 11 because it is LTS. Changes to JDK
> > > will be backported up to september 2023 by the community. If we are
> > > interested in getting updates on OpenJFX also we woul
Den tor. 27. sep. 2018 kl. 22:38 skrev Jan Tosovsky :
> On 2018-09-27 Sverre Moe wrote:
> > Den tor. 27. sep. 2018 kl. 20:06 skrev Johan Vos >:
> >
> > > 3. Stick with an LTS release and get commercial support to get updates
> > >
> > Thanks. Option 3 looks very interesting. It would allow us to
16 matches
Mail list logo
