nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (Commented) (JIRA)" <>
Subject [jira] [Commented] (NUTCH-1200) Resolving Ivy dependencies in several plugins
Date Thu, 01 Dec 2011 12:10:39 GMT


Lewis John McGibbney commented on NUTCH-1200:

Hi Blaise I would direct you to this tutorial [1]. It covers everything you should need to
get Nutch working within your Eclipse IDE. It takes about a half hour or so to set up but
definitely works as I have been debugging some simple jobs from within Eclipse. Please get
back to us on the user lists if you are having any problems. Thank you

> Resolving Ivy dependencies in several plugins 
> ----------------------------------------------
>                 Key: NUTCH-1200
>                 URL:
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.4
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>             Fix For: 1.5
>         Attachments: NUTCH-1200-trunk.patch, NUTCH-1200-v2-trunk.patch
> When configuring Nutch 1.5-SNAPSHOT in Eclipse, I noticed that any plugins requiring
additional libraries OVER AND ABOVE the ones specified in NUTCH_HOME/ivy/ivy.xml cannot resolve
the dependencies. In specific the classes are 
> {code}
> - FeedParser <dependency org="" name="rome" rev="1.0.0" conf="*->master"/>
> - URLAutomationFilter - <dependency org="dk.brics" name="automaton" rev="???"/>
> - SWFParser <dependency org="" name="gwt-incubator" rev="2.0.1"/>
> - HTMLParser   <dependency org="net.sourceforge.nekohtml" name="nekohtml" rev="1.9.15"/>

> {code}
> Further to this, I cannot locate the dk.brics dependency!
> Finally, the plugin/ivy.xml files for the above plugins cannot be parsed corectly due
to the ${nutch.root} vairable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message