Jérôme Charron wrote:
Moreover, I would like to suggest some other javadoc "improvements" (?):
1. Create a group for abstract plugins (like lib-http or lib-regex-filter)
named for instance "Plugins API"
+1
2. Create a group for extensions points (As far as I remember, one of the
first problem when you want
to extend nutch is to found where are the hooks, ie what are the extensions
points). One more time, since the
javadoc groups are filtered by packages, each extension point interface must
be moved to specific package.
The idea is then to move all the core extensions points to a new package
(for instance org.apache.nutch.api).
I'm reluctant to move the extension interface away from the parameter
and return value classes used by that interface. Could we instead add a
super-interface that all extension-point interfaces extend? That way
all of the extension points would be listed in javadoc as
implementations of this interface.
3. Create many javadoc plugins groups (one for each major kind of plugin :
Indexing, Parsing, Protocol, Query, UrlFilter and
Misc for those that cannot be categorized).
+1
Doug
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
