Le 08/11/2012 02:03, Phil Steitz a écrit : > IIUC, Cocoon (and others?) also need this, so it makes sense for it > to be a component on its own and - assuming it stays small - in > Commons. I have not looked carefully at the code, but it does not > look so much like "a crawler" to me as a framework for managing > things like crawlers.
I think it would be better for the project to find a home where the other developers have an expertise in the same domain. Commons is the perfect home for components that are not related to the main concern of many other projects (logging, configuration, pooling...). But in this case there is a project, Nutch, whose core functionality is exactly the goal of the component. That why I think this solution should be preferred. Cocoon could then have a dependency on a nutch-crawling component. Emmanuel Bourg
smime.p7s
Description: Signature cryptographique S/MIME
