Plugin repository management (custom repo support)

• Acceptance Test - Add?:

  No

To facilitate others running their own plugin repositories for plugins not hosted on igniterealtime.org, it would be nice to mirror kind of a debian repository or up2date/yum repository update system where there administrators could specify additional plugin repos alongside the primary one hosted by Jive. This would even allow folk to add in the beta plugins repository for immediate beta updates if that's the kind of thing they wanted.

Couple of things to think about:

• What is the current method of indicating what plugins are available? What exactly does Openfire look at and how does it know?
• Should the primary repo be forced, no way to remove it?
• Need to provide a public spec for how to set up a custom repository of their own and make it functional.