| 17 Jul 2025 |
 Infinidoge 🏳️⚧️ | Amazing, nix-support seemingly has no results in the Nix manual, and 6 entirely different results for things other than remove-references-to | 17:19:42 |
 emily | like bundling in the JDK is explicitly deprecated
As of JDK 11, the javafx.* modules are no longer included as part of the JDK. They are now distributed separately as a standalone, unbundled release of OpenJFX. They are available either as maven artifacts for use with maven/gradle or as a standalone SDK that includes jmod files for use with jlink.
| 17:19:43 |
| emily | nix-support isn't related to move-references-to | 17:20:03 |
| emily | nix-support is just files that stuff in Nixpkgs stdenv etc. consume | 17:20:11 |
| emily | not sure Nix cares about it at all | 17:20:14 |
| Infinidoge 🏳️⚧️ | * Amazing, nix-support seemingly has no results in the Nix manual, and 6 entirely different results for things other than remove-references-to in the Nixpkgs manual | 17:20:32 |
| Infinidoge 🏳️⚧️ | The 6 references are in the nixpkgs manual (edited previous message) | 17:20:47 |
| Infinidoge 🏳️⚧️ | So it isn't documented in the place where it's most useful anyways | 17:20:56 |
 msgilligan | Yeah, but it's non-trivial to build your app correctly pulling JavaFX from Maven. I do it correctly in my apps, but I think there are paying Zulu customers who don't know how to do it or have legacy code that is hard to update. | 17:23:59 |
| msgilligan | I have run into some Nix-specific JavaFX issues that I was able to workaround by using the bundled JavaFX. | 17:25:16 |
| emily | to be clear, I'm not saying "use it from Maven". | 17:27:34 |
