Plugin initialisation failures should be logged with detailed error messages #12
Description
Current behaviour:
If initialisation of a plugin fails, GW logs a 'WARNING: Plugin class could not be initialised.'
, which does not provide any info about the cause of the failure. To investigate further, the user has to debug within GW.
Expected behaviour:
A message providing information about the root cause of the failure should be logged.
Example:
I had one of my plugins failing to initialise because the plugin was trying to create a receiver for a signal with the same name that had already been created by another plugin in the same app. This I found out from the Exception being thrown in PluginManager.initialise(). E.g. such exception messeages could be logged.