No such luck! At the time of writing, it does not exist and probably does not need to, as it would really only obfuscate the actual packager. Let's add the important bit - the packaging plugin. Medusa relies upon JavaFX and needs a module-info attaching that describes that dependency. Notice the significantly expanded modules section. Moditect did do its part: it generated the module-info for our project. Let's see what happens if we try to build the code:įailed to execute goal org.moditect:moditect-maven-plugin:1.0.0.Beta2:create-runtime-image (create-runtime-image) on project Test: Execution create-runtime-image of goal org.moditect:moditect-maven-plugin:1.0.0.Beta2:create-runtime-image failed: Execution of jlink failed -> Say, for example, I wanted to include a dependency that is not modular. That was simple, right? The thing is, projects are not simple! They usually include stuff that is not always at the bleeding edge of development. Note the Test executable and if you execute it, we have our little app.

Navigate through that and you'll see a folder structure similar to the below image. I know, counter-intuitive, right? We are going to use ModiTect, a Maven plugin authored for the very purpose of managing module descriptors and runtime images.Ĭompared to authoring module descriptors by hand, using ModiTect saves you work by defining dependence clauses based on your project's dependencies, describing exported and opened packages with patterns (instead of listing all packages separately), auto-detecting service usages, and more.Īdd the create-runtime-image execution right after the add-module-info execution they will run sequentially.Īt this point, go ahead and run a clean:build again - you'll find it takes a little longer, but this time we are rewarded with a new jlink-image directory in the build location. Next, we are going to start by removing the module-info from the root of the project. In Part 2, we'll use the same project to include jlink, and in Part 3, jpackager. We'll, of course, want to be able to run it like a standard application with an icon and a delivery mechanism. Of course, getting the application to run in the IDE is really only the first stage. You'll be able to break and step as usual. Instead of the classpath, we have the same commands as a regular debug and the module path. New -> Other (if not in the quick picks) -> Java -> Java Module Info. The module-info.java goes in the root folder of the project, NetBeans will helpfully create this for you, but it will need a small tweak once generated to open the module to its dependencies. Let's now change them to create the module. The important thing to notice is that upon including these dependencies, the platform-specific versions are also included.

It will still not run at this point, but we're getting closer. The following illustrates the dependencies needed to get this project to build on the JDK. To be honest, most of the pom.xml can be junked and replaced at this point. This can be done by selecting the project Properties -> Build -> Compile. You can choose the JavaFX Application because it will create the default folder set to house the fxml, etc.Īt this point, the project will not build, so it is a good time to ensure the correct JDK is selected. I am using the latest incarnation from the Apache Software Foundation, version 11.0. We'll do this in maven because of the great integration with NetBeans. Place the jmods inside the module jmods directory of the installed JDK and jpackager binary and supporting jar inside the bin directory. OpenJFX - from here, you'll need the jmods I really struggled to get a clear lead on how to modulize my JavaFX applications on AdoptOpenJDK, therefore, I am going to share a simple configuration for a modular project.įirst off, you will need to grab a few things and move them into the right places: I’ll outline all of the programs, equipment, and information you need from start to finish. Then, you’ll learn how to generate a runtime from Maven before turning to focus on distribution. First, I’ll demonstrate how to modulize JavaFx from NetBeans. In this article, I’ll share with you a comprehensive guide to working with JavaFX with NetBeans.

Install javafx netbeans 12