Hello Lewis, Julien. Solr isn´t the problem. I know that Nutch don´t includes it, so I´ve added it as a Maven dependency aswell. Otherwise, I´ve got a Java project that compiles and deploys a Solr server without problems. The thing is that the parent project (which includes my version of Nutch, another project that uses it to crawl and to execute other operations, and finally a projects that conforms a Solr server) compiles correctly with Maven. The problem happens when crawling from a class that uses the Crawl.java from the Nutch artifact generated as the logs pasted shows... I continue thinking that the problem is centered in the idea that nutch-1.3.job (renamed for me as "nutch-hacked.job") is necesary as nutch-hacked.jar is for a crawling process.
To resume: *Parent project:* . ...... *Nutch hacked project*. When you compile with Maven the artifact generated is a .jar package file, not a .job package file. I check that if you compiles with the build.xml Ant script with the "package" target you both obtain the .jar and the .job package files. . ...... *Solr server project. *Deploys a Solr server to the Tomcat indicated with the Solr configuration desired. . ..... *Crawler and processor project*. It does all the logic and includes the artifact generated from *Nutch hacked project,* but only the .jar artifact, not the .job artifact. The last project is the one that launches the crawling process using the Crawl.java class from the Nutch hacked project. Then it fails. Any idea or suggestion ? :-(
