Doug,
I would love to suggest to create a new project "plugins" in our cvs and store most of the plugins there.I like having a single tree. That way, when an API changes, it's easy to update and test all of the plugins.
To have most of the plugins in a separate cvs project mean not that we can not do daily integration builds about all sources.
I just that newbies are overloaded with this much source folder in one project.
I agree it make sense to take care about API Changes but normally plugin shouldn't affected �by such a change, that why that are plugins.
I think that it would be good to have a minimal nutch and people then can add ftp, pdf, language cc and other plugins.
If we want to disable plugins, we can do that with the plugin.excludes system property. For example, if we want to disable all protocols but http and all parsers but html, we could make the default:
<property> <name>plugin.excludes</name> <value>protocol-(?!http).*|parse-(?!html).*</value> </description> </property>
What plugins do you think should be enabled and disabled by default?
The idea is just make things more handly and do not overload the people with complexity.
We may can handle that until the build process something like a "minimal" and a "complete" task.
As you know there are 2 open point on my issue list until doing them I will come up with a solution suggestion.
Stefan
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
