When a plug-in cannot be instantiated, e.g. because of an API change, VStar should not exit!! It should continue past that point, ignoring the plug-in failure.
This applies to both plug-in loading and the Plug-in Manager in which each plug-in is also instantiated in order to be queried.
Propagating a PluginManagerException upward is actually incredibly unhelpful! A message should be displayed and VStar should continue along its merry way.
Log in to post a comment.