Dear new nutch contributors,
I'm very demotivated to contribute a jmx backbone to nutch since I have the feeling nutch contributors aren't ready for that yet.
I'm sorry to say that, let me explain why I think so.
Stefan,
In OSS projects that's the way sometimes things are... which is not to mean that we shouldn't improve as a community ;-) You've made a lot of valuable contributions, and I personally value highly your involvement in the project, so please don't get discouraged.
Please remember that there was already a PDF, Word, Flash, RTF, Open office etc. content extractor (today we call it parser again ) plugins that was working well and most important they comes with junit tests.
To me it looks like contributors start to understand the power of the plugin system, just count the contributions that comes since it is official available.
This might be the very reason why there were so few comments on the system - it takes a while to understand its full potential.
I'm quite interested in helping you to integrate the other content parsers that you contributed in your original patch.
I have a bad taste in my mouth since all new contributions are new functionality to nutch and comes without any junit test.
Just a critical question, why we write " All Java code modules should be accompanied by JUnit tests." if we just ignore that,
sorry to ask but why is code formatting more important then junit tests?
You have a good point here - JUnit tests will follow shortly for the patches I recently submitted ;-)
The jmx stuff is to much work for just discussing it after implementing it or just ignore it as other patches I had done (topic filtering, snmp, host grouping ... *:-)*).
Using Jmx will dramatically change the complete architecture of nutch but it will be a bigger improvement to nutch architecture then the plugin system.
If you don't trust me just ask the Heritrix Guys for experience they use jmx as well and it looks like they invest a lot of time for a clean architecture design.
I think it's not that people don't want to use JMX, it's just that in my experience very few people actually have experience with using JMX-based systems for day-to-day maintenance and operation. So, the impact and benefits are not immediately obvious...
We haven't tools anymore we will have a server that runs 24/7 and a set of components that can be triggered.
There was just one comment by Doug about my jmx mail and nobody else give any technical comment. That strongly remembers me to the time I was sending my first concept about the plugin system to this list.
See above - I think many of us who hang around on the lists are not too experienced in JMX. Hence, we are not able to provide any sensible comments this or that way - I can at least speak of myself here... ;-)
-- Best regards, Andrzej Bialecki
------------------------------------------------- Software Architect, System Integration Specialist CEN/ISSS EC Workshop, ECIMF project chair EU FP6 E-Commerce Expert/Evaluator ------------------------------------------------- FreeBSD developer (http://www.freebsd.org)
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nutch-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
