You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use the ABAP Cleaner in VSCode, but unfortunately the extension takes the wrong Java runtime. So the start of the daemon ends up in an error message. It's caused by a path in the PATH environment variable pointing to a Java runtime for x32 instead of x64. I cannot change it and the user account environment variables are considered only after the system variables.
So, can you please provide a setting in the VSCode extension to set the Java runtime environment path? Or maybe a special environment variable, that can be used therefore?
this should now be fixed with version 1.29.0, which was released last Friday: both the standalone version and the VS Code extension now include a minimal JVM, making ABAP cleaner independent from whether and where Java is installed otherwise.
Activity
sratz commentedon Jul 21, 2026
Our plan is to include a JVM within the standalone ABAP cleaner and the VS Code extension to avoid these issues altogether: #478
jmgrassau commentedon Jul 27, 2026
Hi Armin,
this should now be fixed with version 1.29.0, which was released last Friday: both the standalone version and the VS Code extension now include a minimal JVM, making ABAP cleaner independent from whether and where Java is installed otherwise.
Kind regards,
Jörg-Michael
Vertumnus commentedon Jul 27, 2026
That fixes my issue. Thank you very much!
jmgrassau commentedon Jul 27, 2026
Hi Armin,
perfect, thanks a lot for the feedback! And all the credits go to Sebastian @sratz 👍
Kind regards,
Jörg-Michael