Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
17.10.0
-
None
-
Unknown
-
Description
Right now, an old plugin installed as an extension is only loaded if it's listed in the static xwiki.plugins property of xwiki.cfg, and plugins are only loaded at startup. This makes it hard to move plugins out of XWiki Standard: an admin who still needs a removed plugin has to install it and also edit xwiki.cfg and restart.
The idea is to introduce a component entry point allowing an extension to declare a plugin that the plugin manager finds even when it's not listed in xwiki.cfg, with the plugin manager reacting to the registration/unregistration of these components to update its list of plugins.
Conclusions of the discussion:
- No configuration to disable such dynamically registered plugins: an admin who doesn't want one can uninstall it.
- The new entry point and the code reacting to its registration events are kept separate from the rest of oldcore, so that they can move to legacy together with the plugin manager later.
Attachments
Issue Links
- relates to
-
XWIKI-9825 Allow XWikiPluginManager to find plugin installed as extension
-
- Closed
-