On  6 Nov, Marcel Ruff wrote:
 
     
2. It has its LogPluginInfo (stolen from PluginInfo - but without
logging).
    
         
What about keeping our PluginInfo, remove all unnecessary logs and only
keep the single log.warn().
       
Sorry, I was unclear (and tired). The problem with PluginInfo is not so
much the logging, but that it's construcor requires a PluginManagerBase.
Our plugin manager is however not based on PluginManagerBase, because of
the logging problem, and therefore it can not be used as an argument
when creating PluginInfo.