Hi, I am sorry for a belated reply.
My opinion: merge CND and cpplite. I.e. roughly: merge what is needed from the cpplite cluster into the cnd cluster, and drop the rest. I assume the CND would, at least for now, use an LSP server to provide the editor features. The LSP server setting from cpplite.editor should be under the CND's C/C++ options. The data loaders (cpplite.editor/.../file) should be dropped, the LSP bindings (and the SPI for configuration, i.e. cpplite.editor/.../spi, which should probably be kept), either placed in some reasonable module under the CND cluster, or cpplite.editor could be moved into the CND cluster and possibly renamed (cnd.lsp?). I assume cpplite.debugger will be used, that should be moved, I think (please double-check with Martin Entlicher). Regarding cpplite.project - note sure to what degree we need to keep it. In the first phase, we might just remove the ability to create new cpplite projects, but these only exist in the userdirs, which makes things easier to drop. FWIW, cpplite.debugger uses a bunch of classes from CND, please see cpplite/cpplite.debugger/external/cpplite-mi-1.0-SNAPSHOT.jar - we should include them in the source form from CND and take them through IP Clearance with the rest of the CND code. I can try to help with some of these, if needed, when I have time. Jan On Sat, Jan 8, 2022 at 3:04 PM antonio <[email protected]> wrote: > Hi all, > > As you may know we're polishing a subset of the cnd donation (with an > editor with lexer, folding, formatting, the C/C++ makefile projects and > the toolchain (as well as dlight). > > The fact is that both cpplite and cnd clash in the "commit-validation" > test when both of them want to create the "Options/C++" dialog pane (see > https://issues.apache.org/jira/browse/NETBEANS-6372). > > It seems we could handle this in different ways: > > Option 1: > > Use a "weight" attribute in layer.xml registration [1], so both > "cpplite.editor" and "cnd.editor" can register the "C/C++" pane, but > only one "wins" depending on the weight. Sadly this attribute is not > currently supported in the OptionsDialog (nor in commit-validation > test?), and adding it just for this corner case seems too much, I think. > > Option 2: > > Make "cpplite.editor" depend on "cnd.editor". This will make the cpplite > cluster depend on the cnd cluster (currently only cpplite is in the > "release" set). > > Option 3: > > Make "cnd.editor" depend on "cpplite.editor". This will make the cnd > cluster depend on the cpplite cluster. > > > So, what say? Any preferences? Any alternatives? > > Thanks, > Antonio > > P.S.: Option 2 is available at > https://github.com/apache/netbeans/pull/3428 > > > [1] > https://bz.apache.org/netbeans/show_bug.cgi?id=141925 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
