Community
Participate
Working Groups
To allow CDT to use LSP4E's debug adapter work, we need a way to have an extended debug adapter protocol in LSP4E.
New Gerrit change created: https://git.eclipse.org/r/145740
Gerrit change https://git.eclipse.org/r/145740 was merged to [master]. Commit: http://git.eclipse.org/c/lsp4e/lsp4e.git/commit/?id=ebb4ea676dd0ed1f658a7e156ceaff8f1ed7accf
Cool, thanks. Can you try to add a note about it in the "themes" for upcoming releases: https://projects.eclipse.org/projects/technology.lsp4e/releases/0.11.0/edit ? It's where I usually put the N&N-like items so far.
Done. This is what I put in as a first pass: An extender of the LSP4E debug may have some extensions to the Debug Adapter Protocol they want to expose in Eclipse with additional UI elements. For example, a memory view can be enabled in the UI if the extender's extensions to the DAP support reading and writing memory. To allow this extenders can extend DSPLaunchDelegate, overriding the new createDebugTarget method. Within that method a specialized version of the DSPDebugTarget can be used that enables extended functionality. To make this easier, the DSPDebugTarget can be extended, overriding createLauncher, to create an LSP4J launcher that uses the extended interfaces.