jenv | Java enVironment Manager

I have followed a lazy, not-best-efficient, yet useful, strategy. Since dealing with docx is less flexible than html, I converted the markdown md to html first, then moved from html to docx like this:

Found that you need to register the java-17 dist in jenv using command:

which java is often used to find the exact executable you are calling when you type in java.

Keep in mind that when you type in the command java your JAVA_HOME setting is not used. Rather, the operating system PATH setting is used. If you have an older copy of java "before" the one you want to use on the path, then that's what the operating system will give you. To fix a problem like this, you need to alter your path such that the directory of your desired java version comes before any other java versions.

I do see that you checked your PATH setting, but I think you didn't know what to check, because you only listed directories. In those directories, a java executable exists. If the old executable comes in a directory earlier in the path, that's the version of java you will get when running it from the command line, regardless of any other settings.

Now, it is still important to have the JAVA_HOME set correctly, because when various Java tools want to discover items, thy might read JAVA_HOME (and if it is wrong, get directed to a non-matching JVM).

The OP's error message "The plugin install found problem timeout of loading Java ME Web Service Clients" is misleading, since it suggests that there may be a network issue. However, the FileNotFoundException in the NetBeans log file shows that the real cause is that the plugin installer is failing because it can't locate the file unpack200.exe to unpack the downloaded plugins.

This issue arises if NetBeans is running on JDK 14 or greater, since unpack200.exe was removed in that release. See JEP 367: Remove the Pack200 Tools and API for details.

A workaround in the past has been to temporarily run NetBeans with an earlier JDK which contained unpack200.exe, typically JDK 8 or JDK 11. Then, once the plugins had been successfully installed, just revert to using your JDK >= 14. That approach is documented in great detail here. Most of the individual steps in that answer remain valid, but there is no longer any need to revert to running NetBeans on a JDK < 14 because there is a simpler approach available.

When running NetBeans 12.5 on a JDK >= 14, the plugin installer now detects that unpack200.exe is missing after downloading the plugins, and invites you to provide an instance of it:

Clicking the Choose Unpack200... button in the lower left of that screen opens the following dialog:

Navigate to any instance of unpack200.exe on your machine. It will reside in the bin directory for any JDK release < 14. Once the plugin installer has located an instance of unpack200.exe it can convert the downloaded plugins into jar files to complete the plugin installation process.

Notes:

• Although this question is about the Java ME plugins, the same approach applies when running NetBeans on a JDK >= 14, and installing any plugin that uses the Pack200/Unpack200 APIs.

• NetBeans asking for a location of unpack200.exe only happens once. Thereafter it uses the location you provided initially by default.

I went into the ~/.bash_profile I made and deleted everything from it

Just needed bri.xgbRegressionModel.setMissing(0.0F) and now it works

Those are not a complete time properties and read at runtime. That's why you get the JVM version which is used to run the program

The answer is right in the runnodes script file:

The documentation explains that -Dquarkus.native.container-build=true option means that you want to build a Linux executable and that the build should happen in a container. You can even control the runtime for that Docker/Podman with: