[ http://issues.apache.org/jira/browse/NUTCH-215?page=comments#action_12367180 ]
Jerome Charron commented on NUTCH-215: -------------------------------------- The primary meaning of the plugin dependency is to specify that a plugin rely on the code of another plugin, not that it must be executed after a plugin it depends on. I think that in some particular cases (as in yours), this concept of plugin order is important, and it is really an issue. But I don't think it is the right way for solving it. We should think about a more generic/secure solution (a parse plugin must not be allowed to be declared to be called before a protocol plugin, a plugin can implement many extension points, ...). For a short term workaround, you can for instance directly call the plugin that you need to be called before yours. +1 for this issue to be solved, but -1 for this patch. Jérôme > Plugin execution order > ---------------------- > > Key: NUTCH-215 > URL: http://issues.apache.org/jira/browse/NUTCH-215 > Project: Nutch > Type: Improvement > Versions: 0.8-dev > Reporter: Enrico Triolo > Priority: Minor > Attachments: plugin_order.patch > > This patch allows nutch to automatically guess the correct order of execution > of plugins, depending on their dependencies. > This means that, for example, if plugin A depends on plugin B (as stated in > the plugins.xml file), then B will be executed before A. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
