This message is in part related to an ongoing discussion on the commons-dev mailing list, the debate being whether a new validator package should be included into commons when Turbine, for instance, already has intake, and it might make more sense to migrate that into commons instead. Here's a representative thread. http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101036144030278&w=2
Over on our side, I understand Aaron's in the process of importing JCS (http://jcs.sourceforge.net) into Turbine (stratum, I think?). Now I recently discovered that Jakarta actually has not one but _TWO_ existing caching subsystems, one at Commons and another at Cocoon (which according to http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101045218126806&w=2, are somewhat different and are complementary). With the addition of Aaron's JCS, Jakarta will likely have 3 caching subsystems. I'm not totally sure what the status of the other projects are. Errmmm...the question I guess is, what's the policy, if any, on a situation like this, where multiple projects have existing codebases which duplicate functionality and purpose? Should we go ahead with the original plan, or maybe wait for a conclusion to be reached over at commons-dev? Personally, I can't wait (in _every_ sense of the word) for the caching to be imported and work to begin on integrating it with Torque but that's for purely selfish reasons of course...:) Regards, Kelvin Tan Relevanz Pte Ltd http://www.relevanz.com
