On Thu, 15 Oct 2026 at 11:24, Anton Epple <[email protected]> wrote: > That matches what I had in mind for our part. I offered to provide the Java > tools (usages, refactorings with a compile check, compile errors) to an MCP > server inside the IDE, and they are already released on their own schedule > elsewhere (a standalone server and a VS Code extension). It allows us to > "move fast and break things" unlike we would do inside the NB code base.
So if we can change that to "their own schedule *here*" then we have the potential for moving fast and breaking things, while still having the benefit to being under the ASF / Apache NetBeans umbrella. > Shipping them as a NetBeans plugin as well, with the option to merge later > once things have settled and there is interest, seems the right way to me. > What would help in the IDE itself are small API additions such as the > workspace/folder concept Jarda and Michael are discussing, so that such > plugins don't each have to build it themselves. I'm mostly with Michael's position on being pro-project camp there. And keeping groups somewhat orthogonal to that. While still having a basic project type that can be used for all these things being discussed. Although we also don't make enough of groups supporting configuration at the moment - the only thing we have currently is a Maven home setting that may or may not work correctly. We should probably keep that part of the discussion in one place, not fifteen. :-) Best wishes, Neil --------------------------------------------------------------------- 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
