nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <>
Subject [jira] Updated: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory
Date Fri, 07 Apr 2006 20:15:24 GMT
     [ ]

Chris A. Mattmann updated NUTCH-245:

    Summary: DTD Schemas for plugin.xml configuration files in conf directory  (was: XML Schemas
for xml configuration files in conf directory)

> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>          Key: NUTCH-245
>          URL:
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is
independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor

> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it,
and most people just go look at an existing plugin's plugin.xml file to determine what are
the allowable elements, etc. There should be an explicit plugin DTD file that describes the
plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory
later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy)
generate plugin.xml files that can then be validated. I'm also going to post another issue
regarding adding an addition to the ant target that builds the Nutch website. The addition
to the ant target would copy the existing DTD files in $NUTCH_HOME/conf to the Nutch website
ROOT. That way, we could then reference the DTD file in all the XML instance files by reference
something like <!DOCTYPE system "">,
within the parse-plugins.xml, or similarly for the nutch-site.xml, or mime-types.xml file.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message