Console for Camel LSP Server remains open after deletion of the project about camel-lsp-client-eclipse HOT 7 CLOSED

I think it is a classical behavior of Eclipse.
If this behavior needs to be changed in the specific context of Language Servers, I would say that it needs to be done in LSP4E project

from camel-lsp-client-eclipse.

Facing the same problem here.
I have to edit multiple pom.xml files today. For every file, a new console is opened, and never closed.
This behavior is especially annoing once you have to scroll through the list of consoles because too many of them are open.

In this example, the list is taking up the entire height of my screen.

from camel-lsp-client-eclipse.

I can't believe it's Eclipse standard as I don't see any other behaving like Camel LSP:

• opens a new language server process for what it seems every XML file I have (not every project and not every Camel file)
• opens a new console for each process (good luck finding your application's, see screenshot above)
• these consoles stay open forever and they also never show me anything
• after exiting Eclipse the language server processes stay open...

I just disabled the two Camel LSP servers in Eclipse settings, the hassle is much too big for the benefits.
I'm using both Red Hat Developer Studio 12.9 and Spring Tool Suite 4.1 with different Java 1.8 versions, same behaviour.

from camel-lsp-client-eclipse.

I guess the Camel Language Server does use the logMessage() operation which exactly requests client to log that to the user if not mistaken. So not invoking this method should avoid such logging.
About the multiplicity, the camel language server could investigate declaring support for workspaceFolders in its capabilities. This is used by LSP4E to determine whether to spawn a new LS or whether one can be reused for files which are under a different Eclipse project.

from camel-lsp-client-eclipse.

I guess the Camel Language Server does use the logMessage() operation which exactly requests client to log that to the user if not mistaken. So not invoking this method should avoid such logging.

thanks. I created this PR to avoid this logging which is not very useful, especially for end users camel-tooling/camel-language-server#205

I think that LSP4E should be able to close the different console when there is no more resources attached to it in the workspace. I will try to report an enhancement request soon (but we are too close to weekend time :p)

About the multiplicity, the camel language server could investigate declaring support for workspaceFolders in its capabilities. This is used by LSP4E to determine whether to spawn a new LS or whether one can be reused for files which are under a different Eclipse project.

Thanks for the pointer. I created camel-tooling/camel-language-server#206

from camel-lsp-client-eclipse.

The console is not opening anymore with latest version.

Thanks for the report @tsedmik and for the push @Postremus @sorin-costea and for the help @mickaelistria

from camel-lsp-client-eclipse.

verified - Apache Camel LSP Client Extensions Plugin 1.0.0.201902121537

from camel-lsp-client-eclipse.