In message <[EMAIL PROTECTED]>, Henr i Yandell writes: >This is also short-sighted. There is a very strong language barrier >between Java and other languages. It's not a wonderful thing to have, but >pretending that it's the same strength as C to Tcl, or Perl to Python will >just ostracise the Java [read Jakarta] bits more.
Here's my take. Consumers of libraries just want canned code that solves a problem they're facing. They don't care if the code happens to reside along with other libraries written in/for different languages. After categorizing by functionality, you still have to subcategorize by language so a programmer doesn't download a C++ theorem proving library when he needs one in Lisp (nevermind that a C or C++ library can offer multiple language bindings--an approach I would favor for Apache Commons projects). I don't believe Jakarta Commons/XML Commons/etc. projects should be forced to move into Apache Commons (if that's what we're talking about), but I believe some of their components would be better served in Apache Commons once it gets off the ground. I may have lost the point of the discussion, in which case just ignore what I said. daniel
