I might have overlooked something in the whole flood about this topic.
Allow me to add that a move into Apache Commons might have our Java flavour sort of shaded. A move out of Jakarta Commons, however, might free our projects from the "server-only" orientation of Jakarta project in general.
This orientation is stated somewhere in a charter I think. I remember having it weaved at me everytime I was requesting that some component of Jakarta Commons could be applet friendly.
I don't think any of jakarta-commons are actually server-only...
Paul
On 21-Dec-03, at 20:24 Uhr, Dirk Verbeeck wrote:
The answer to the question "how would a Jakarta Commons TLP differ from an Apache Commons TLP?" is simple. The only difference would be that J-C does focus on java and A-C also includes other languages.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
