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
Maven is not only about editing XML, one can also launch a build. This is currently done my m2e for example, but I'm wondering if not lemminx-maven would be the better place using the Debug Adapter Protocol?
I'm asking this because I currently explore to add support for real "debug" of maven runs, e.g. putting a breakpoint in the XML to stop at a given mojo execution, I did this before with cucumber-eclipse but then hand coded it, here I'd like to maybe right away start with DAP and try to investigate where it is best placed.
As the lsp4j integration of the DAP seem to also support running a process (without debug) it seems m2e could even here delegate some work to lemminx-maven.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Maven is not only about editing XML, one can also launch a build. This is currently done my m2e for example, but I'm wondering if not lemminx-maven would be the better place using the Debug Adapter Protocol?
I'm asking this because I currently explore to add support for real "debug" of maven runs, e.g. putting a breakpoint in the XML to stop at a given mojo execution, I did this before with cucumber-eclipse but then hand coded it, here I'd like to maybe right away start with DAP and try to investigate where it is best placed.
As the lsp4j integration of the DAP seem to also support running a process (without debug) it seems m2e could even here delegate some work to lemminx-maven.
Beta Was this translation helpful? Give feedback.
All reactions