Closed smileBeda closed 1 year ago
Did you clone the repo? The release file contains the jar files. If I extract those first this issue won't appear for me.
It is too long ago to remember how but I believe I did it with some package installer on SublimeText, no idea anymore, and since it never worked + there was really not much interaction anyway on the topic, I removed it. I think I followed the steps in some Discuz forum, where this thing was announced.
@martijndeb where does the cloned release go to? Why is this not - like anything else in sublime text packages - done automatically? Why is this not in the Readme?
It sounds fishy that I have to manually download or clone the release, and then put it (where?).
Putting the release into the Sublime Text 3 > Packages folder seems to have resolve that error.
Frustrating that this is not mentioned anywhere and remains a variable that no one knows if it is even needed.
Amazing. No more JAR files included in the cloned git or whatever. I am not a specialist of Sublime Text packages, but now not even anymore cloning the package to the packages will work Latest release is of 2020, latest commit of 2022
What a mess.
I installed Java, then the LSP SonarLinter, when saving a file it throws:
Full console stack: