commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject Re: Commons Core (was RE: [pattern][lang] Cross dependecy)
Date Fri, 09 Aug 2002 18:33:10 GMT

I'm not very sure - the idea is to pick the commons components you need
in a project. This is getting harder.

What would be the criteria to include in core ? What if you have multiple
components doing the same thing ( perfectly acceptable in commons ) ?

I'm not very comfortable with too many interdependencies ( and recursive
dependencies ) in the commons. IMO some packages are becoming bloated,
and we may turn into a spaghetti mess.


Berin Loritsch wrote:

> I also like the idea of a commons core.  However we do run the problem
> of
> what to put in there.  I like the idea of importing one medium sized JAR
> as
> opposed to several mini-JARs for my projects.  If that means that
> Commons
> Core has Pattern, Lang, Collections (nice package), and *possibly* CLI,
> I think that Commons Core would be an excellent package.
> However the charter would be difficult to manage.  If Core is strictly
> an
> integration project, we have to draw the lines of what gets integrated.
> Unless of course, Core is something that will build a custom JAR for
> you based on the other Commons projects.  I think that would rock for
> a general useability standpoint, but from a maintenance and release
> standpoint, it would be a nightmare.
> Anyhoo, Core is a nicety and something I would like to see happen.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message