Hi Neil, 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.
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. Toni Am 15.10.26, 12:11 schrieb "Neil C Smith" <[email protected] <mailto:[email protected]>>: Hi, On Wed, 14 Oct 2026 at 14:52, ehsavoie <[email protected] <mailto:[email protected]>> wrote: > I've been playing around to use Agent Client Protocol to connect a coding > agent into NetBeans. ... > [1]: https://github.com/apache/netbeans/pull/9712 > <https://github.com/apache/netbeans/pull/9712> I put the needs-discussion label on the PR, but only just having a chance to follow up myself. I don't have a lot of time for NetBeans right now, and I've been concentrating the time I do have on getting us ready for freeze, hence reviewing and labelling. Thanks for looking into this area. However, I have major reservations about merging this into the main IDE repository. There may be a few module changes / moves that should be there though. IDE and platform releases are large and time consuming, mostly down to one person (Eric) now that the release team is no longer, and really it's enough to keep to the quarterly schedule. Pushing updates between releases is awkward, and with the current way the Maven releases are architected, overly resource intensive. Features like this, with both rapidly changing ecosystem and potential security considerations, feel like they would benefit from a lighter and more responsive release schedule. It's been discussed in another context, but I think this is another feature that would be good to consider releasing via an official plugin repository (ie NetBeans' own extensions). Being in extra is pointless as it'll never be released. Not that this appears to be in extra anyway?! Just like Maven plugins have their own repositories and release schedules, let's consider which features of the IDE are better addressed in that way? I'm also curious what the "Signed off by" line on each commit means for the provenance of the code in this PR? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] <mailto:[email protected]> For additional commands, e-mail: [email protected] <mailto:[email protected]> For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists> --------------------------------------------------------------------- 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
