B4J Question Compile B4J app with standalone packager

[max123]

Hi all,

here my log when compile my app with B4J standalone packager. The package is successfully created using openjdk 19.0.2,
but I see this message on the log:

Only Java 11, 14 and 16 are supported (Tools - Configure Paths).

Is this just a typo error ?

The full log:

B4JPackager11 Version 1.40
Exe name: SM-Link.exe
Only Java 11, 14 and 16 are supported (Tools - Configure Paths).
build folder: C:\Users\Massimo\DOCUME~1\PROGET~2\MIEIPR~1\MIDI-L~1\Objects\temp\build
InputJar: C:\Users\Massimo\Documents\PROGETTI_B4J\MIEI PROGETTI\MIDI-LINK\Objects\result.jar
Running: C:\Users\Massimo\DOCUME~1\PROGET~2\MIEIPR~1\MIDI-L~1\Objects\temp\FindDosPath.exe
Running: C:\java\jdk-19.0.2\bin\jar
.
Package name: b4j.example
Running: C:\java\jdk-19.0.2\bin\jdeps
.
Explicitly excluded modules: [javafx.web]
Included modules: [java.base, java.desktop, java.logging, java.prefs, javafx.base, javafx.controls, javafx.fxml, javafx.graphics, javafx.media, javafx.swing]
Running: C:\java\jdk-19.0.2\bin\javac
.
.
.
Running: C:\java\jdk-19.0.2\bin\jar
.
Running: C:\java\jdk-19.0.2\bin\jlink
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Running: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\csc.exe
.
Running: explorer.exe
.
Done!

 

[Erel]

Are you using latest version of B4J - 10.2? It should be fixed there.

 

[bdunkleysmith]

@Erel if I explicitly define the complier path:

#JavaCompilerPath: 21, C:\Java21\jdk-21.0.7\bin\javac.exe

or

#JavaCompilerPath: 24, C:\Java24\jdk-24.0.1\bin\javac.exe

but leave the path pointing to C:\Java19\jdk-19.0.2\bin\javac.exe in the Paths Configuration modal:

Using 10.2 I also see that message:

Only Java 11, 14 and 16 are supported (Tools - Configure Paths).

Is that expected behaviour?

 

[max123]

Are you using latest version of B4J - 10.2? It should be fixed there.

@Erel, no I use B4J 10.00.
Ok, I will update it next. I only wanted to know if just a typo.
Now you fixed it, so this is good.

Thanks
Have a good day
Max

 

[Erel]

Is that expected behaviour?

The message should show java 19 as well. Anyway, you can ignore it. It just means that I haven't tested it with Java 20+.