As more people develop plugins, it's natural that they want to provide their own
update centers to deliver module updates (like
http://www.liguorien.org/javascripteditor/ )

Unfortunately, it's fairly painful for users of such 3rd party update centers to
register the custom update center. You can see the pain in
http://blogs.sun.com/geertjan/date/20060113

It's one thing for a module author to go through some pains to set up a custom
update center, but it's entirely another for all the users of such custom update
center to go through this much trouble.

This needs to be easier.

Several ideas:

- define a custom file extension and MIME type for update center XML. Then
NetBeans installer could register itself against those MIME types and provide
GUI to add a custom auto update center. The end user experience would be:

   1. Alice the module author sets up her web server to return a proper MIME
type or just use the right extension. Her netbeans module project page will have
a prominent link.
   2. Bob will click that link.
   3. His IE or Firefox asks him to launch an application. He'll say yes.
   4. a small application starts and ask him if he really wants to register this
update center. He says yes.
   5. a new update center gets registered.
   6. Bob is happy because the installation was easy.
      Alice is happy because her users are happy.