There is an javafx use flag on openjdk:17, but no corresponding openjfx:17 package. Reproducible: Always Steps to Reproduce: 1. emerge -av dev-java/openjdk:17 Actual Results: [ebuild N ] dev-java/openjdk-bin-17.0.3_p7:17::gentoo USE="alsa cups gentoo-vm -headless-awt (-selinux) -source" 187,026 KiB [ebuild NS ] dev-java/openjdk-17.0.3_p7:17::gentoo [8.332_p09:8::gentoo, 11.0.15_p10:11::gentoo] USE="alsa cups gentoo-vm%* jbootstrap (system-bootstrap) (-big-endian) -debug -doc -examples -headless-awt (-javafx*) (-selinux) -source -systemtap" 102,342 KiB Expected Results: [ebuild N ] dev-java/openjdk-bin-17.0.3_p7:17::gentoo USE="alsa cups gentoo-vm -headless-awt (-selinux) -source" 187,026 KiB [ebuild NS ] dev-java/openjdk-17.0.3_p7:17::gentoo [8.332_p09:8::gentoo, 11.0.15_p10:11::gentoo] USE="alsa cups gentoo-vm%* jbootstrap (system-bootstrap) (-big-endian) -debug -doc -examples -headless-awt javafx (-selinux) -source -systemtap" 102,342 KiB
From profiles/base/package.use.mask: # Georgy Yakovlev <gyakovlev@gentoo.org> (2021-10-16) # openjfx for openjdk17 is not yet available dev-java/openjdk:17 javafx
Using this, https://openjfx.io/openjfx-docs/#install-javafx, to point to the installed version of openjfx:11 with openjdk:17 seems to work, so the versions don't seem to be tied together.
Yes, we need to package 17 and drop 11 completely. Jfx17 should work with jdk11. However, packaging jfx is enormous, frustrating amount of work and patching, and fighting with gradle/portage interaction. I currently lack time and will to package it. Also jfx11 is vulnerable and stable-masked so it’s better to drop it and not use with jdk17.
Right now there are even later openjfx releases, than 17.
Err, did not notice, jfx17 was mentioned along with packaging hardness.
openjfx 21 is also missing for dev-java/openjfx:21.
*dev-java/openjdk:21
