I’m glad that jpackage that originated in JavaFX made it into the JDK at least. :-)
I moved to JavaFX as soon as JavaFX 2.x was available. I have no intentions of ever using Swing again. (Recent discussions about the binding API for Swing being missing for the NB GUI builder come to mind. I’m glad I don’t have to worry about that anymore.) Lots of things have been removed from the JDK at this point: Activation, JAXB, JAX-WS .. they caused me far more pain as they were “demodularized” when they were removed so you couldn’t get them back as modules anymore. That may be fixed now, but in new packages that aren’t compatible with old code. It makes sense to split up the modules, but it is an inconvenience for sure I think the original plan was to remove Swing at some point as well. JavaFX was just less disruptive than removing Swing. I just wish the “desktop” module was better organized so I don’t have to pull in a bunch of AWT/Swing stuff when I only want to use JavaFX. If the modules were a bit more isolated Swing and JavaFX could evolve at their own pace independent of the core libraries. I really wish there was a better way to deal with JMODs as external dependencies, since both JavaFX and Swing rely on native libraries as well, JMOD is the right mechanism to share them, but there is no “Maven repository” equivalent for them (yet). ImageIO is another thing that should be replaced so it doesn’t tie in to the GUI framework. I.e. just deal with buffers or byte [] at the ImageIO layer and have the helper methods in the GUI frameworks to convert to their specific image type. It’s unfortunate that there is image loading code in Swing/AWT, and JavaFX, and ImageIO all bloating the JRE and with their own quirks and bugs. Lots of stuff could be better in hindsight, but isn’t that always the way? Regards, Scott > On Feb 10, 2022, at 1:00 PM, Thomas Wolf <tjw...@gmail.com> wrote: > > Totally off-topic: does anyone find it ironic that the successor to Swing was > taken out of the JDK while Swing itself survives? Makes me feel rather good > about never having jumped on the JavaFX bandwagon. We currently have a > cross-platform desktop app in beta and the GUI is written in Swing - > packaging the app with jpackage became a whole lot easier after we decide to > remove the one JavaFX component we did use (the chart library) and replaced > it with JFreeChart. > > sorry for the off-topic musing. > tom > > > On Feb 10, 2022 at 12:11:16 PM, Scott Palmer <swpal...@gmail.com > <mailto:swpal...@gmail.com>> wrote: >> Java 11 does not contain JavaFX. You should use the Gradle or Maven >> plugins, or use a JDK that has added the JavaFX modules (Such as the “full” >> Zulu JDK from Azul). >> I strongly recommend migrating away from Ant if you are refreshing the >> project to use modern tools. >> >> Scott >> >>> On Feb 9, 2022, at 6:25 PM, Robert Lockwood <rnlockw...@gmail.com >>> <mailto:rnlockw...@gmail.com>> wrote: >>> >>> I have a Java application from some years ago using an old Netbeans, >>> JavaFX, Scene Builder, and Java 8. I've been asked to add features to and >>> thought that I would migrate it to a more current IDE etc. and put an end >>> to the warnings I receive when I build. I'm using macOA Monterey and an >>> Apple Silicon M1 macBook. >>> >>> I've managed to fix all the syntax errors with help from Dr. Google but >>> cannot complete a build. It cannot find the executable or the deployment >>> library in the JDK. I've supplied the locations in the libraries and jars >>> list and have added the path to the Java Home folder in /Library/... (as a >>> side issue Netbeans cannot find the javadocs). >>> >>> I don't know what I missed and what to try next so I'm asking for help >>> here. First time use of this mailing list, too. The application won't be >>> deployed BTW. I understand the Nashorn warnings. >>> >>> Path to JDK /Lbrary/Java/JavaVirtualMachines/jdk-11.0.2.jdk added to $PATH >>> >>> Build output slightly edited with '***' prepended to warnings and errors of >>> note: >>> >>> *** Warning: java executable not found in JDK, evaluating java executable >>> in RT instead. >>> init: >>> deps-clean: >>> Updating property file: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/built-clean.properties >>> Deleting directory >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build >>> clean: >>> init: >>> deps-jar: >>> Created dir: /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build >>> Updating property file: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/built-jar.properties >>> Created dir: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/classes >>> Created dir: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/empty >>> Created dir: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/generated-sources/ap-source-output >>> Compiling 9 source files to >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/classes >>> Copying 5 files to >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/build/classes >>> compile: >>> < 14 Nashorn warnings > >>> Warning: Nashorn engine is planned to be removed from a future JDK release >>> >>> Copying 11 files to >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/dist/lib >>> *** : java executable not found in JDK, evaluating java executable in RT >>> instead. >>> Detected JavaFX Ant API version 1.0 >>> >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/nbproject/jfx-impl.xml:3550: >>> The following error occurred while executing this line: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/nbproject/jfx-impl.xml:3578: >>> The following error occurred while executing this line: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/nbproject/jfx-impl.xml:3597: >>> The following error occurred while executing this line: >>> /Users/nate/NetBeansProjects_12/FireMapperMetadataTool_12/nbproject/jfx-impl.xml:524: >>> Error: >>> *** JavaFX deployment library not found in active JDK. >>> >>> *** Please check that the JDK is correctly installed and its version is at >>> least 7u4 on Mac or 7u6 on other systems. >>> BUILD FAILED (total time: 7 seconds) >>
