Ticket #1445 (closed defect: fixed)

After some discussion it was decided that the plugin service will not run a given plugin instance. Instead if the user desires to run a plugin instance they will be responsible for populating all its fields and and call plugin.run() directly.

The general approach is for a plugin to also have a constructor that takes an ImageJ context. From there it can find all the services it needs (and fail gracefully if not). Then the user runs publicly provided setters as needed followed by run().

We could simplify the the assignment of services by placing it in a base class (like DynamicPlugin or a new class like DirectPlugin). This base class could walk it's Parameter list and populate all Service fields.

Some work associated with this ticket:
1) perhaps remove a lot of direct api already defined by plugins

If yes then try to take as much code out of the plugin and place in a service.

2) alternatively keep the direct api but define all the context based constructors