jbang.home folder seems to be ignored

[jeffmaury]

Although I have defined jbang.home in workspace settings, the command Synchronize JBang and seems to ignore the path:

[fbricon]

It's a known limitation ;-)

jbang.home: Specifies the folder path to the JBang directory (not the executable), eg. ~/.sdkman/candidates/jbang/current. On Windows, backslashes must be escaped, eg C:\ProgramData\chocolatey\lib\jbang. Used by the JBang: Create a new script wizard and the Run JBang code lens. Useful in case jbang is not automatically picked up from the $PATH, for some reason.

Now for the reason why it's not used by the backend: JBang support acts as a JDT.LS extension, it's not a self-contained LS in itself. Hence, only preferences starting with java. are sent to JDT.LS, and can be used by the JBang-eclipse backend.
So either we rename jbang.home to java.jbang.home, which is a bit awkward, from a UX standpoint, or we send the jbang.home value via a custom command to the backend, but that won't work until after project import.

[jeffmaury]

It's a known limitation ;-)

jbang.home: Specifies the folder path to the JBang directory (not the executable), eg. ~/.sdkman/candidates/jbang/current. On Windows, backslashes must be escaped, eg C:\ProgramData\chocolatey\lib\jbang. Used by the JBang: Create a new script wizard and the Run JBang code lens. Useful in case jbang is not automatically picked up from the $PATH, for some reason.

Now for the reason why it's not used by the backend: JBang support acts as a JDT.LS extension, it's not a self-contained LS in itself. Hence, only preferences starting with java. are sent to JDT.LS, and can be used by the JBang-eclipse backend. So either we rename jbang.home to java.jbang.home, which is a bit awkward, from a UX standpoint, or we send the jbang.home value via a custom command to the backend, but that won't work until after project import.

Which would be fine in this case as Synchronize JBang is related to a project. But I don't know if there are other commands performed by JDT.LS that are not project related and that requires jbang.home

[fbricon]

project import (and the JBang builder subsequently) runs jbang info tools, so it would need to get the proper setting 1st.