Currently, the crawler monitors the configuration file, detects changes, and reloads the file when it changes. We'd like it to do the same thing for plugins, so that when an updated plugin is dropped into place, the new plugin is loaded and used, rather than requiring a crawler restart to incorporate plugin changes.
Currently, the crawler monitors the configuration file, detects changes, and reloads the file when it changes. We'd like it to do the same thing for plugins, so that when an updated plugin is dropped into place, the new plugin is loaded and used, rather than requiring a crawler restart to incorporate plugin changes.