Jesse wrote: > > With NBCode people will be able to get the goodies of NetBeans (Maven > > projects > Probably off topic for this thread, but this part caught my eye. Do I > get it right that in addition to exposing the NB Java parser to Code, > > https://github.com/apache/netbeans/blob/9f2b595df801547c53292952199609ff3ab9 > ec99/java/java.lsp.server/src/org/netbeans/modules/java/lsp/server/Server.ja > va#L129-L174 > > ensures that classpath determinations as made by the likes of > > https://github.com/apache/netbeans/blob/9f2b595df801547c53292952199609ff3ab9 > ec99/java/maven/src/org/netbeans/modules/maven/classpath/CompileClassPathImp > l.java#L50-L65 > > are also considered definitive? If so, neat, though this only offers a > tiny portion of the NB project system’s functionality.
Yes, understanding classpath of various project types is the major benefit use using NetBeans. Neil wrote: > I'd prefer to see LSP support actually in the JDK If the LSP Java support was done in JDK, then it couldn't understand `pom.xml`, neither `build.gradle`, etc. It would be pretty limited. By using NetBeans one gets the understanding of common project types for free. Moreover it is extensible, so we can have OpenJDK project support and possibly also "mx" project support (for understanding Graal sources without any generated). We'll see what other NetBeans goodies we can benefit from. -jt --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
