The effort is not porting parts of NetBeans to VSCode but make them available via Language Server Protocol. So NetBeans runs on backend as the language server and VSCode uses it primarily for Java development. This particular PR is to display in VSCode similar project structure like in NetBeans by enabling the nodes to be part of LSP and then render by VSCode tree view.
The end game is : 1. Any changes done in NetBeans for LSP and VSCode are not done at the cost of “core” NetBeans features. They build on it. 2. Having NetBeans Language Server enables NetBeans for other scenarios in the future like running in some distributed client server architecture like browser java ide. Basically similar to what Eclipse JDT Language Server does. 3. More NetBeans usage, more contributions, more users…. Hope this helps to explain it. Martin > On 16. 8. 2021, at 15:45, Glenn Holmer <[email protected]> wrote: > > On 8/16/21 8:14 AM, Geertjan Wielenga wrote: >> Wait, but this is not news, right? There have been multiple releases now of >> the VS Code integration from Apache NetBeans. > > The question stands. It was prompted by "Let's share significant parts of the > UI in VSNetBeans", which seems to indicate that larger parts of NetBeans are > now being ported. > > Who is driving the effort to port parts of NetBeans to VSCode and what's the > end game? > > -- > Glenn Holmer (Linux registered user #16682) > "After the vintage season came the aftermath -- and Cenbe." > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!YKDVdHUIiLDuwSpIs-gzZ59Gyar_f1mVIFEu0G15I3-jITYlLXbmpw0MapaRQnYOUA$ > >
