My 2c:
Instead of talking it would be easier to create another repository, say
"jakarta-utils" ( or just use jakarta-tool since it's there :-), and start
organizing the reusable code in avalon, turbine, tomcat, etc.
I don't see any problem with having 2 connection pools - as long as both
are self-contained and easy to pick and use.
The problem is when in order to get a connection pool you have to take the
whole package, and it depend on other 10 components.
It's a huge difference between a "CPAN" where you can get the component
you need ( Graph.pm, GDU.pm ) and what I see here - a XXX where you
have to download the whole archive to use one component.
IMHO the problem is in the way the code is organized - low level
components should be in a common repository ( jakarta-util ), each with
it's own directory and minimal external dependencies. ( plus explicit list
of deps ). If we'll have 5 connection pools, each having specific
advantages - that's great, having to choose is not bad. All commiters
to individual projects should be automatically commiters to util,
and we should periodically scan the projects for "general-purpose" code
and move it to jakarta-util.
( probably we'll get 5 StringManagers - but at least they'll be next to
each other )
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
