One small correction: Oracle builds of JDK 20 are built using Xcode 12.4
+ MacOSX SDK 11. The result is the same: builds of JDK from Oracle will
not hit this problem (at least not yet; we will likely update the
compiler some time in the JDK 21 time frame).
-- Kevin
On 1/18/2023 10:57 AM, Johan Vos wrote:
Hi,
I'm trying to understand the severity of this. If I understand it
correctly, the issue (which is really a bug, no question about that)
only occurs when running with a JDK that is built with XCode 14.1 (and
MacOS SDK 13).
Is that correct? If so, are there JDK builds out there that are built
with XCode 14.1? From the docs/building.md file in openjdk, I believe
the daily builds (by Oracle) are done using Xcode 10.1. I don't know
what Oracle and others are using in their JDK releases, but I would be
surprised if all of them are building with XCode 14.1?
Do you control which JDK is used, or is it up to your users to pick a
JDK and then use that one? If users are using a really recent version
of the JDK (built with Xcode 14.1) it seems to me they can also easily
use a really recent version of JavaFX (20-ea)?
I am probably missing something, so it would be good to get a better
understanding of the context?
I totally agree that we have to make it as easy as possible for
end-users to run JavaFX applications, so we should consider whatever
is required to achieve this.
Thanks,
- Johan
On Wed, Jan 18, 2023 at 5:04 PM Glavo <zjx001...@gmail.com> wrote:
After looking forward to it for a month, I was happy to see the
release of OpenJFX 19.0.2, but I was surprised to find that the
update log did not contain JDK-8296654.
I want to know whether this problem has been solved in OpenJFX
19.0.2?
I think this is a very serious problem that needs to be repaired
urgently.
OpenJFX 20 will not be released until a few months later, and it
is no longer compatible with JDK 11, so we cannot wait until that
time to update it.
If 19.0.2 does not include the fix of JDK-8296654, can I ask you
to release 19.0.2.1?
