On Fri, Jul 09, 2004 at 06:25:04PM -0700, [EMAIL PROTECTED] wrote: > On Wed, Jul 07, 2004 at 12:57:19AM -0700, [EMAIL PROTECTED] wrote: > > On Tue, Jul 06, 2004 at 12:48:13PM -0700, Doug Cutting wrote: > > > [EMAIL PROTECTED] wrote: > > > >Currently, the definition of one external parser requires > > > >synchronized change of both file ./nutch/build/plugins/parse-ext/command > > > >and ./nutch/build/plugins/parse-ext/plugin.xml. Ideally > > > >it'd better be handled solely by file plugin.xml. However that would > > > >require attributes in plugin.xml be passed to ExtParser.java, and > > > >I could not figure out a proper way to do it with current plugin system. > > > >Stephan and Doug: any suggestion? > > > > > > Yes, I agree it would be better if a plugin implementation could access > > > the attributes easily from plugin.xml. Perhaps we should make > > > ParserFactory.getExtension() public, then you can call getAttribute() on > > > the returned Extension. Would that work? > > It does not do what I want. > > Anyway I have added junit test to previous patch. > Now it is a new one (20040709, attached below, also > available at http://nutch.neasys.com/patch/) > If no one objects, I will commit it to cvs in two days. > > John
It's in cvs now. So are junit tests for msword and pdf parsers. John ------------------------------------------------------- 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
