Feature Request: abap-cleaner.exe / standalone abap cleaner: create alternative ways to provide java.

[JoachimRees]

abap-cleaner.exe needs a certain java-version (currently: 17), thats well documented and easy to optain (e.g. sapmachine ).
But it seem the only why to "provide" that jave to the abap-cleaner.exe is via path variable (also well documented) .

As there might be cases where people can not set path varaiables, I would apprechiate alternative ways to "provide" the current java.
(And also, if another, OLDER Java ist in the path, too - which will "win"? )

Those ways come to mind, any one of them would be fine:

Via abap-cleaner.ini:
-java_path
C:\tmp\sapmachine-jre-25.0.2_windows-x64_bin\sapmachine-jre-25.0.2\bin

Via sub folder:
If a sub folder "java" exist where abap-cleaner.exe is, first look if there is a javac -> if so: use this.

Via command line argument:
abap-cleaner.exe ---java_path=C:\tmp\sapmachine-jre-25.0.2_windows-x64_bin\sapmachine-jre-25.0.2\bin

Hope some of this is possible.
Joachim

[sratz]

I made a proposal to include a JRE in the stand-alone app: #478.

This increases the size of the downloads but having a self-contained app is typically best practice.

[JoachimRees]

Oh, thanks @sratz , you mention there something I didn't know (nor find) as of now: "'-vm' parameter in
abap-cleaner.ini. "
-> this is exaclty one of the things I was looking / hoping for.

This as first lines in abap-cleaner.ini - works fine for me:

-vm
C:\tmp\sapmachine-jre-25.0.2_windows-x64_bin\sapmachine-jre-25.0.2\bin

[JoachimRees]

And with that knowledge, I now realise the command line argument works juste fine as well:

Via command line argument, cmd:
abap-cleaner.exe -vm C:\tmp\sapmachine-jre-25.0.2_windows-x64_bin\sapmachine-jre-25.0.2\bin

-> nice, I think I can close this, it's solved for me.