#464 Plug-in instantiation errors should not cause VStar to exit!

Defect
closed-fixed
None
9
2014-09-27
2014-08-09
David Benn
No

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.

Discussion

  • David Benn

    David Benn - 2014-09-22
    • assigned_to: David Benn
     
  • David Benn

    David Benn - 2014-09-27
    • status: open --> closed-fixed
     
  • David Benn

    David Benn - 2014-09-27

    Fixed in 2.16.4

     

Log in to post a comment.