From: Arron Bates [EMAIL PROTECTED]
The Commons project itself is now housing separate sub projects which
have seemingly their own boundaries Every little part is acting like its
own jakarta project. Hell, the votes are even working that way... This
guy's been doing some great work with
I know what you mean, but I'm not sure that commoncommons is the answer.
IMHO, code in the commons falls into three categories -
- Widely used, and often as a group (BeanUtils, Betwixt, Collections,
Digester, Logging)
- Individual stable, less interrelationships (CLI, Cactus, DBCP, HTTP
Client,
Hi,
I think the most simple solution is to split redistributables like
commons-collections.jar
commons-transform.jar
.
It is nothing bad if some common class is maintained in collections.
This requires agreement from collections as its not
