> 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.
That's correct! But it was so convenient to use the update center ;-) > > 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. Update center that can download anything RELEASE260 versioning from org.netbeans namespace would be a good solution. Not sure where to put the update.xml.gz file? Somewhere on Maven as well - a .gz file can be one of the artifacts, I think. Or it could be done without XML. update.xml is just one of possible implementations of some https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-autoupdate-services/index.html interface. -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
