The only defecency is that if one is running, that it considers the
      entire pliugin to be running. I'm not sure if that is a good thing
      or a bad thing, but the other code checks threads that way.

    Loading a class would be one of them!
    So we do a quick check first, If it bombs out, we delay and try again.
    If it bombs after that, then we throw the ClassNotFoundException.

      - Set classpath for specific client only, not for the whole JVM
      - Use ConfigDir() not AppDir()

      - Make target=_blank for plugin links

      - Always show start button for webapps and plugins
    * configclients.jsp, configupdate.jsp:
      - Fix submission when entering CR in a text box
    * Plugins:
      - Stop all plugins at shutdown
      - Log tweaks
    * WebApps:
      - Remove the WAC after stopping it
      - Stop a WAC before starting it to prevent dups

      - Negative delay means run immediately and inline
      - Add methods to test class and run inline,
        to propagate errors to the console
      - Add javadoc for clients.config format
      - Use new methods for plugins

      - Fix plugin start button
      - Change signer prop to match docs
      - Tweaks

      - Fix classpath setting for webapps
      - Implement uninstall args in clients.config

      - Hook up update/delete/check/save buttons
      - Implement delete
      - Hide unless router.enablePlugins=true

      - Check plugin key against all installed plugins
      - Reword some error messages
    * VersionComparator: add '-' and '_' as valid separators
      to better support plugin and java version checking