Official Jaunch breaks Java compilation in Fiji Script editor

[scouser-27]

The official version of Jaunch provided with Fiji breaks the ability to compile Java-based plugins from within the Fiji Script editor.

If I discard the official version of Jaunch and insert an early beta-testing copy of it from c. February 2024 (into the same copy of Fiji), compiling works correctly again.

@ctrueden raised this as an issue on the SciJava tracker:
scijava/scripting-java#14

However the functionality change occurs with the version of Jaunch used, not with SciJava.

details of the differences in the --dry-run output between "Official" and "Unofficial" are available:
https://forum.image.sc/t/fiji-latest-java-21-bundles-ready-for-community-testing/112417/65?u=scouser27

The issue appears to apply regardless of the JDK version used:
"Unofficial" works fine with both system-installed OpenJDK21 and also the pre-packaged Zulu21 provided in default copies of Fiji [i.e. not the No-JRE version]

[ctrueden]

Can't compile Java in the Script Editor

@odinsbane fixed this today and I released a new version of scripting-java, uploaded to Fiji-Latest. If it's still broken, let me know.

You can also drop a .java file into a subfolder of scripts, for example scripts/Image/Process_Pixels.java, and it will be added to the menus and compiled on the fly to run it.

Pre-compiled plugins won't run under “Official” Jaunch

If you change the Jaunch configuration like this:

diff --git a/config/jaunch/fiji.toml b/config/jaunch/fiji.toml
index b2d2aaa9a..90ad463a1 100644
--- a/config/jaunch/fiji.toml
+++ b/config/jaunch/fiji.toml
@@ -116,10 +116,10 @@ jvm.classpath = [
     # Construct the classpath.
     '${app-dir}/jars/*.jar',
     '${app-dir}/jars/*/*.jar',
-    '--plugins|${plugins}/*.jar'
-    '--plugins|${plugins}/*/*.jar'
-    '!--plugins|${app-dir}/plugins/*.jar',
-    '!--plugins|${app-dir}/plugins/*/*.jar',
+    '--plugins|${plugins}',
+    '--plugins|${plugins}/*',
+    '!--plugins|${app-dir}/plugins',
+    '!--plugins|${app-dir}/plugins/*',
     #'${user.home}/.plugins/*.jar',
     #'${user.home}/.plugins/*/*.jar',
     #'${user.home}/.share/fiji/jars/*.jar',

Then when you drop a .class file into plugins or a subfolder thereof such as plugins/Analyze, the plugin will appear in the Plugins menu or corresponding subfolder thereof. Note that as per original ImageJ requirements, the filename will need an underscore _ somewhere for it to be discovered.