Actions
Architecture #13036
closed
Remove the need for Spring in plugin
Status:
Released
Priority:
N/A
Assignee:
Category:
Plugins integration
Target version:
Fix check:
Regression:
Description
Currently, we use spring to manage the loading of plugins.
This is mostly a liability, and the only real use case for spring here is to locate the plugin definition classes and load them.
So, we could remove spring for all of that, which means we would only have spring for authentication (and only that!).
Updated by 
Updated by
Actions