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
When LemMinX-Maven is stable enough, I’ll have to update vscode-xml-maven to consume it.
Great!
Since the Java plugin for VSCode by Red Hat brings m2e, the required dependencies of LemMinX-Maven might be present on the VSCode side.
I think it will be very difficult to use the JAR from vscode-java.
Otherwise we could make an uber jar of LemMinX-Maven to bring in these dependencies. This is something we’ll have to test when we get there.
Yes please.
More with redhat-developer/vscode-xml#251 we will able to avoid developping a vscode extension, juste define a user settings which links the lemminx-maven uber jar and that's all.
Okay no worries, we can create an uber jar :) I think this is a good solution as it will make integration of LemMinX-Maven into other LSP clients (eg. Emacs) much simpler.
When LemMinX-Maven is stable enough, I’ll have to update vscode-xml-maven to consume it.
Since the Java plugin for VSCode by Red Hat brings m2e, the required dependencies of LemMinX-Maven might be present on the VSCode side.
Otherwise we could make an uber jar of LemMinX-Maven to bring in these dependencies. This is something we’ll have to test when we get there.
The text was updated successfully, but these errors were encountered: