I disagree. I think plugins should be configured by the same mechanism as everything else. That way nearly all of a site's customizations are in a single file, nutch-site.xml, and, when they update to a new version of Nutch they won't lose their customizations. In general, folks shouldn't change files that are in CVS, and the plugin.xml is in CVS, authored by developers, not by users.OK, it make sense to have all of them in a central place. However I person think that the nutch-default | site.xml is already a huge file.
You have to scan carefully the file for searching important values.
What do you think about one configuration folder but a file for each plugin?
Stefan
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
