On Thu, 26 Jun 2025 at 14:28, Jaroslav Tulach <jaroslav.tul...@gmail.com> wrote: > I see. I was afraid of some decision like that. It breaks the "IGV workflow" - > e.g. ability to install all NetBeans modules into application that doesn't > distribute them.
Well, it was discussed on the dev@ list a few months ago, and prior to that on Slack and amongst people involved in releases. The key thing that has been discussed a lot over the last couple of years is that the release process is overstretched, and we either need more involvement or to do less. This unfortunately ended up with doing less. Mind you, given the conversations that led to that decision, that it affects the "IGV workflow" is somewhat ironic! :-) The usage stats of the update centre were part of that decision. The update centre is a lot of extra work, for almost no usage, not to mention some infrastructure issues with how it was configured. It does push some work on to the small number of platform projects that were relying on it being there. We were mainly considering legacy Ant build downloads rather than projects registering the UCs themselves though. > > The NBM should be on Maven, so a custom update.xml could be produced > > to download from there? > > The problem is that I need the `update.xml` sooner than my module is > installed. Well, I was thinking more that a useful task could be an update.xml that is generated from and points to the Maven artefacts. That could happen here, it could happen elsewhere (eg. on the IGV side). Applications would still need to register it though. > PS: another problem is 3rd party update center - IGV "inherits" it from > NetBeans. Those NBMs are be available, but their dependencies may not - > because the standard update.xml is empty... Another problem is any application using things from the NB cluster. I know there was a conversation a while ago about dropping that cluster from the Maven artefacts. IMO, no other application should be picking up the branding and infrastructure requirements of the IDE, and the stability of those resources should only be considered in the context of the IDE's needs alone. Best wishes, Neil --------------------------------------------------------------------- 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
