Currently all plugins and connectors that fail to load at startup are deleted from the config. This may happen when e.g. a plugin throws an exception at startup, the plugin jar is missing. While for normal users this isn't that big of a deal because plugins shouldn't usually fail to load. But for developers this can be very annoying, because each time this happens they have to recreate their plugin and also set all requirements which when there is a high count (for example our testall plugin) annoyes as this time adds up.
For now we should still keep all plugins and show them in the gui, even if they fail to initialize. This way the user can see the error by reading the log, fix it, restart and still has his config. Incase they actually don't want an plugin instance anymore they still can delete it using the gui. If the plugin fails to load they just shouldn't be able to start and manage the instance.
With the new gui we should also show the exact error which caused the plugin to not load using the gui but for now the above mentioned changes would already be a huge improvement in terms of UX.
Description
Currently all plugins and connectors that fail to load at startup are deleted from the config. This may happen when e.g. a plugin throws an exception at startup, the plugin jar is missing. While for normal users this isn't that big of a deal because plugins shouldn't usually fail to load. But for developers this can be very annoying, because each time this happens they have to recreate their plugin and also set all requirements which when there is a high count (for example our testall plugin) annoyes as this time adds up.
For now we should still keep all plugins and show them in the gui, even if they fail to initialize. This way the user can see the error by reading the log, fix it, restart and still has his config. Incase they actually don't want an plugin instance anymore they still can delete it using the gui. If the plugin fails to load they just shouldn't be able to start and manage the instance.
With the new gui we should also show the exact error which caused the plugin to not load using the gui but for now the above mentioned changes would already be a huge improvement in terms of UX.
References
The new gui: #44