Hi PJ, I can only reinforce what Chris said about 1) Not being a pain, and 2) Helping out with the proposed work. If something can be proposed which makes good sense and which adds value to the project then it is an overwhelming possibility that a development effort will back such a proposal. Of the threads that Chris has provided, I would ask you to take a look at NUTCH-609 in particular. This is very interesting but as you can see has lacked any recent development drive.
Thanks On Mon, Nov 21, 2011 at 11:16 PM, Mattmann, Chris A (388J) < [email protected]> wrote: > Hey PJ, > > You aren't being an ass at all. You're asking an important question, and > something I've been interested in for a while. > Here are some relevant threads to take a look at: > > http://wiki.apache.org/nutch/Nutch2Architecture > > http://www.mail-archive.com/[email protected]/msg12688.html > > http://www.slideshare.net/chrismattmann/lessons-learned-in-the-development-of-a-webscale-search-engine-nutch2-and-beyond > https://issues.apache.org/jira/browse/NUTCH-609 > http://osdir.com/ml/user.nutch.apache/2011-07/msg00080.html > http://5341.com/list/48/349985.html > > If you're interested in contributing to Apache Nutch, check this great > guide out written by Dennis Kubes: > > wiki.apache.org/nutch/Becoming_A_Nutch_Developer > > Before there wasn't a ton of interest in replacing the plugin system since > it "worked" and we didn't get a lot of > complaints or anything. That interest turned into the perception that a DI > framework wouldn't be welcome. > On the contrary, I'd say if you figured out how to get a DI framework > working with the existing plugin system, > I can personally say I'd dedicate some of my time towards helping you > shepherd it in and I think the > rest of the committers would be on board. > > Thanks for your interest. If you have any more questions, please ask! > > Cheers, > Chris > > > On Nov 21, 2011, at 1:14 PM, PJ Herring wrote: > > > Hey, > > > > So I am admittedly a noob with Nutch, but have spent some time digging > through the source code. I am just curious if anyone has talked about, in > future developments of Nutch, replacing the whole way we register plugins? > I ask because I am using Nutch on a project with Maven. At the moment I > have to copy a whole bunch of JAR files with there plugin.xml files into a > certain directory on build, which is fine, but is kind of breaking the > whole Maven paradigm. It would be nice to have some sort of Maven > repository where plugins lived, and then wire up which plugins I want to > use using some kind of DI framework, like Spring or Guice. Then instead of > writing XML Plugin Descriptor Files, every plugin could write a class > extending PluginDescriptor and register its self with the PluginRepo, or > something of the sort. > > > > Also, I have never contributed to an open source project, so if I am > being an ass I don't mean to be. Just would love to help make a great tool > better in any way. > > > > Best, > > PJ Herring > > > > > > > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > -- *Lewis*
