[lsp][plug-in] Ease the integration of a new LSP into Eclipse Che with plug-ins

[benoitf]

Description

Eclipse Che is becoming more and more extensible and customizable.

Workspace.next engine is allowing to plug new tool container into the workspace
Theia and plug-in model is allowing an easy way to plug new IDE components as well. (instead of Theia extension)

Goal of this epic is to get advantages of these two when we talk about LSP implementations.

Plug-in's model API should provide LSP plug-ability for the client side. (like the textmate configuration, the lsp options, etc)
Definition of the container providing LSP server should be a workspace.next configuration.

All of this should be then packaged as a Che Plugin.

Tasks

• define LSP Theia plug-in API
• check workspace.next configuration with a plugin
• documentation on writing Che plugin with ws.next part + theia plugin.
• video demo of this e2e flow.

[tsmaeder]

define LSP/theia API (it could be che API if specific to Eclipse Che)

Please no! Let's keep make it so that we can take any lsp, package it in a container and then run it as a che plugin. Special Che API would be counter to that goal.

[benoitf]

@tsmaeder how do you will bring syntax highlight and other stuff ?
also "what kind of sabotage" are you seeing ?
AFAIK today there is IDE plugin for each language on Che.

@tsmaeder maybe you need to edit as well your comment because it looks like it's only a "inline quote of myself"

[tsmaeder]

Maybe I don't get it: there is already api to contribute syntax highlighting in Theia. Why would we add something incompatible?

[benoitf]

@tsmaeder I don't know if you read too quickly but it would be only if there is something specific to che that we could require a Che API (like grabbing the url of a container, getting some container metadata, or anything else specific due to Che and Theia integration).

Also AFAIK for now syntax highlighting is through extension not plug-in model.

to sum-up, goal is more to provide Theia "plug-in" model to LSPs.

[benoitf]

@tsmaeder I've updated the description of the issue

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.