Hi Andrzej, Yep, +1. I also want to make a small update, where instead of creating a new NutchConf object, to just pass it through (maybe via the protocol layer?). Does this make sense?
Cheers, Chris On 3/8/07 1:47 PM, "Andrzej Bialecki (JIRA)" <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/NUTCH-384?page=com.atlassian.jira.plugin > .system.issuetabpanels:comment-tabpanel#action_12479442 ] > > Andrzej Bialecki commented on NUTCH-384: > ----------------------------------------- > > +1 - although the patch needs whitespace cleanup before committing > (indentation should be 2 literal spaces, "if" keyword should be separated by > one space from the parens). > >> Protocol-file plugin does not allow the parse plugins framework to operate >> properly >> ----------------------------------------------------------------------------- >> ------ >> >> Key: NUTCH-384 >> URL: https://issues.apache.org/jira/browse/NUTCH-384 >> Project: Nutch >> Issue Type: Bug >> Affects Versions: 0.8, 0.8.1, 0.9.0 >> Environment: All >> Reporter: Paul Ramirez >> Assigned To: Chris A. Mattmann >> Attachments: file_protocol_mime_patch.diff >> >> >> When using the file protocol one can not map a parse plugin to a content >> type. The only way to get the plugin called is through the default plugin. >> The issue is that the content type never gets mapped. Currently the content >> type does not get set by the file protocol. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nutch-developers mailing list Nutch-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nutch-developers
