I've written a windows script which works very similar to the standard nutch shell script.
I'd rather we not have to maintain two versions of this script, one shell and one batch. New commands would have to be added in two places, which is a recipe for things getting out of sync.
Did you have a problem with the cygwin version? Or did you just not want to have to install and run cygwin? That's reasonable, I guess.
A better way to do this might be to replace most of bin/nutch with a Java tool that examines the command name, and then calls the appropriate class's main(String[]) method. Then we could have both shell and batch scripts which just setup the classpath and then run this class. We still end up duplicating the JVM configuration logic, but that should change a lot less often than the command set. Would someone be interested in building this?
Also, if you have trouble sending attachments to the list then attach things to a bug report instead. Attachments are far easier to process than inline stuff in email.
Thanks,
Doug
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
