You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@nutch.apache.org by Paul Tomblin <pt...@xcski.com> on 2009/07/31 04:04:59 UTC
Plugin development
How do I develop a plugin that isn't in the nutch source tree? I want
to keep all my project's source code together, and not put the
project specific plugin in with the nutch code. Do I just have my
plugin's build.xml include $NUTCH_HOME/src/home/build-plugin.xml?
(I'm a little shakey on ant syntax, I'm used to make.) Other than
that, and making sure my plugin's jar file ends up in nutch's
CLASSPATH, is there anything special I need to know?
Should I be asking this on the developer list?
--
http://www.linkedin.com/in/paultomblin
RE: Plugin development
Posted by Ar...@csiro.au.
> -----Original Message-----
> From: ptomblin@gmail.com [mailto:ptomblin@gmail.com] On Behalf Of Paul
> Tomblin
> Sent: Friday, July 31, 2009 9:49 PM
> To: nutch-user@lucene.apache.org
> Subject: Re: Plugin development
>
> On Fri, Jul 31, 2009 at 4:33 AM, Alexander
> Aristov<al...@gmail.com> wrote:
> > What do you mean under putting it in the nutch source tree.
>
>
> I mean those instructions you linked to (which I had already seen)
> only show you how to compile your plugin if you're willing to put it
> in $NUTCH_HOME/src/nutch/plugin, which I am not. I want to be able to
> compile it in my own source tree. I don't need to put my servlet code
> in the Tomcat source code tree to compile it, and I don't need to put
> my Swing code in com/javax, so I shouldn't need the source code tree
> of Nutch just to compile a plugin.
You can compile your plugin anywhere you want, as long as it has required interfaces and does what it is expected to do. Then you make a jar file and place it in a separate folder in Nutch plugins folder, together with plugin.xml file. See how it is done for other plugins.
>
> --
> http://www.linkedin.com/in/paultomblin
Re: Plugin development
Posted by Paul Tomblin <pt...@xcski.com>.
On Fri, Jul 31, 2009 at 4:33 AM, Alexander
Aristov<al...@gmail.com> wrote:
> What do you mean under putting it in the nutch source tree.
I mean those instructions you linked to (which I had already seen)
only show you how to compile your plugin if you're willing to put it
in $NUTCH_HOME/src/nutch/plugin, which I am not. I want to be able to
compile it in my own source tree. I don't need to put my servlet code
in the Tomcat source code tree to compile it, and I don't need to put
my Swing code in com/javax, so I shouldn't need the source code tree
of Nutch just to compile a plugin.
--
http://www.linkedin.com/in/paultomblin
Re: Plugin development
Posted by Alexander Aristov <al...@gmail.com>.
What do you mean under putting it in the nutch source tree.
If you alter nutch you will change some parts of it anyway. you don't need
to put all source files to nutch, instead you may develop then as a separate
project but you include it to nutch in configuration + add jar file. But
nutch plugins do the same
Best Regards
Alexander Aristov
2009/7/31 Paul Tomblin <pt...@xcski.com>
> That assumes that you're going to be putting the plugin in the Nutch
> source tree. I'm looking for guidance on what to do differently if
> you don't put it in the nutch source tree.
>
>
> On Fri, Jul 31, 2009 at 12:48 AM, Alexander
> Aristov<al...@gmail.com> wrote:
> > This is a simple HowTo
> > http://wiki.apache.org/nutch/WritingPluginExample-0.9
> >
> >
> > Best Regards
> > Alexander Aristov
> >
> >
> > 2009/7/31 Paul Tomblin <pt...@xcski.com>
> >
> >> How do I develop a plugin that isn't in the nutch source tree? I want
> >> to keep all my project's source code together, and not put the
> >> project specific plugin in with the nutch code. Do I just have my
> >> plugin's build.xml include $NUTCH_HOME/src/home/build-plugin.xml?
> >> (I'm a little shakey on ant syntax, I'm used to make.) Other than
> >> that, and making sure my plugin's jar file ends up in nutch's
> >> CLASSPATH, is there anything special I need to know?
> >>
> >> Should I be asking this on the developer list?
> >>
> >> --
> >> http://www.linkedin.com/in/paultomblin
> >>
> >
>
>
>
> --
> http://www.linkedin.com/in/paultomblin
>
Re: Plugin development
Posted by Paul Tomblin <pt...@xcski.com>.
That assumes that you're going to be putting the plugin in the Nutch
source tree. I'm looking for guidance on what to do differently if
you don't put it in the nutch source tree.
On Fri, Jul 31, 2009 at 12:48 AM, Alexander
Aristov<al...@gmail.com> wrote:
> This is a simple HowTo
> http://wiki.apache.org/nutch/WritingPluginExample-0.9
>
>
> Best Regards
> Alexander Aristov
>
>
> 2009/7/31 Paul Tomblin <pt...@xcski.com>
>
>> How do I develop a plugin that isn't in the nutch source tree? I want
>> to keep all my project's source code together, and not put the
>> project specific plugin in with the nutch code. Do I just have my
>> plugin's build.xml include $NUTCH_HOME/src/home/build-plugin.xml?
>> (I'm a little shakey on ant syntax, I'm used to make.) Other than
>> that, and making sure my plugin's jar file ends up in nutch's
>> CLASSPATH, is there anything special I need to know?
>>
>> Should I be asking this on the developer list?
>>
>> --
>> http://www.linkedin.com/in/paultomblin
>>
>
--
http://www.linkedin.com/in/paultomblin
Re: Plugin development
Posted by Alexander Aristov <al...@gmail.com>.
This is a simple HowTo
http://wiki.apache.org/nutch/WritingPluginExample-0.9
Best Regards
Alexander Aristov
2009/7/31 Paul Tomblin <pt...@xcski.com>
> How do I develop a plugin that isn't in the nutch source tree? I want
> to keep all my project's source code together, and not put the
> project specific plugin in with the nutch code. Do I just have my
> plugin's build.xml include $NUTCH_HOME/src/home/build-plugin.xml?
> (I'm a little shakey on ant syntax, I'm used to make.) Other than
> that, and making sure my plugin's jar file ends up in nutch's
> CLASSPATH, is there anything special I need to know?
>
> Should I be asking this on the developer list?
>
> --
> http://www.linkedin.com/in/paultomblin
>