Hi all, This is really good news. If we can phase out jdt.ui and may be make it a light weight UI layer just to support additional custom JDT protocol parts in LSP, the JDT.LS will heavily benefit since we don't need to always change both jdt.ui and jdt.ls when we need to implement a new feature.
Best regards, Gayan. On Fri, Nov 18, 2022 at 12:43 PM Mickael Istria <mist...@redhat.com> wrote: > Hi all, hi Gayan, > > I'm reviving this old thread that is the most relevant place to share some > progress: > In https://github.com/rgrunber/eclipse.jdt.ls.client (there is a p2 repo > linked), you can see some progress on the topic of using JDT-LS in Eclipse > IDE. > Currently, it just starts JDT-LS externally, from a separate installation > as a separate process (similarly to what Wild Web Developer does with > LemMinX); but it already does a decent bit of work that way. In the code, > you can also find code that has tried to start JDT-LS in the same process > as the workspace, and this seems to be both tricky and technically > interesting; some issues were reported to JDT-LS about how this kind of > integration can be made to work, but this is not trivial. The first > iteration was then to keep the easier separate-process approach, but I (and > others are welcome to join) will try to keep investigating having JDT-LS in > the same process because I see major potential benefits in this. > Cheers, > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev >
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
