Hi Laurent,
I see that the Java2D fix was just pushed to jdk/jdk. Now that the JDK
fix is in, I'll review it this week. It will need a second reviewer
(maybe Phil or Sergey?)
There isn't an openjfx-11 updates repo available. When / if there is,
this seems a good candidate...
-- Kevin
On
Hi,
As a general rule I'm fine with that but as outlined in another reply we
should only break building with older JDKs in case it really adds value.
So I think we should official define the JDK N-1 and JDK N but don't pro
actively break JDK N-2, ... if there's no real value.
Tom
On 24.09.18
In general, I think developers updating from JavaFX 11-12-13 are also
capable of updating the JDK from 11-12-13, so I prefer the coupling
1. Allow building JavaFX N with either JDK N-1 or JDK N.
This is also my preference.
-- Kevin
On 9/24/2018 12:12 AM, Johan Vos wrote:
> And
>
>
> > And it's only going to get worse as time goes on. Would it not be
> > possible to support up until the last JDK LTS(Starting at 11) release
> > for building JavaFX? I feel like maybe that would be more reasonable.
>
> This is a good question, and maybe in the future we might not be so
>
Auto-update and a packager are different things.
Both are needed, but at this moment, there is only a JEP for the packager.
I think it would be wise to have a standard (hence a JEP) for auto-update
as well, as the use case you describe is not unique...
- Johan
On Sun, Sep 23, 2018 at 8:40 AM
