Hi Silvio, you're right, the plugins are compiled into tmp_build, but the relevant plugin.xml files are in the src/plugin sub-folders. By setting the value of the plugin.folders property in the nutch-site.xml file to "./src/plugin" it picks up the plugin.xml information from there. Did you change this property from the default value "plugins"?
Hope this helps. Kind regards, Martina -----Ursprüngliche Nachricht----- Von: Silvio Heuberger [mailto:[EMAIL PROTECTED] Gesendet: 03 December 2008 11:45 An: [email protected] Betreff: Re: AW: Ideal development environment for nutch plugins? The main problem seems to be, that since the plugin java source folders are on the eclipse build path, they end up compiled into tmp_build. Now they are missing the plugin.xml file, and as a result are not picked up by the PluginManifester class. I'm trying to figure out a way, to rectify this situation. Martina (or anyone else), have you solved this before? Greetz Silvio Silvio Heuberger wrote: > Hi Martina > > I knew that changes to the config files would not be picked up until a > full rebuild of the project (or as a matter of fact, until I copy them > over to the tmp_build directory.) > What substantially contributes to my current headache is the fact, that > suddenly I had ClassNotFoundExceptions and now the crawler ignores urls, > that it did not ignore as of yesterday. > I will definitely have to set my own SVN repo up, for the work on the > plugin. Then I can tag versions that do run, just in case something goes > bad again. Right now, the crawler is useless if started from Eclipse. If > started from the command line, it works as inteded, however the plugin > does not yet. I figure this is because the special fields I extract from > the documents are not yet added as fields to the lucene documents. > But as long as Nutch is not debuggable, there is no telling... >
