nutch-extensionpoints not in plugin.includes

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

nutch-extensionpoints not in plugin.includes

Stefan Groschupf-2
Hi developers,

in nutch-default.xml property plugin.includes we say: "  In any case
you need at least include the nutch-extensionpoints plugin."
But we do not include it by default.
    <value>protocol-http|urlfilter-regex|parse-(text|html|js)|index-
basic|query-(basic|site|url)|summary-basic|scoring-opic</value>
We may be should update the text or include the plugin everything
else may be confuse users.

Should I open a bug or can someone with write access just jump in and
fix that.

Thanks,
Stefan
Reply | Threaded
Open this post in threaded view
|

Re: nutch-extensionpoints not in plugin.includes

Andrzej Białecki-2
Stefan Groschupf wrote:

> Hi developers,
>
> in nutch-default.xml property plugin.includes we say: "  In any case
> you need at least include the nutch-extensionpoints plugin."
> But we do not include it by default.
>    <value>protocol-http|urlfilter-regex|parse-(text|html|js)|index-
> basic|query-(basic|site|url)|summary-basic|scoring-opic</value>
> We may be should update the text or include the plugin everything
> else may be confuse users.
>
> Should I open a bug or can someone with write access just jump in and
> fix that.

I may - but since you know the details of the plugin subsystem, tell me
what _should_ be there? I.e. should we really include it in the
plugin.includes list, or not?

--
Best regards,
Andrzej Bialecki     <><
 ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com


Reply | Threaded
Open this post in threaded view
|

Re: nutch-extensionpoints not in plugin.includes

Stefan Groschupf-2
> I may - but since you know the details of the plugin subsystem,  
> tell me what _should_ be there? I.e. should we really include it in  
> the plugin.includes list, or not?

This is a philosophically question.
I personal prefer restrict definitions, since applications behavior  
is better traceable. That was a reason I implemented the plugin  
system in a restrict way.
Later on this was washed out by the plugin.auto-activation mechanism,  
what I still think was not a good move.

However in the moment we have the situation that nutch-
extensionpoints is not included but the the auto activation mechanism  
includes this plugin since it is used by all other plugins.
So if you switch of auto activation today with default configured  
plugin-includes nutch will crash.
My person point of view is to add nutch-extensionpoints and switch  
off auto activation. .. but this is just my personal point of view...


Stefan