"Rodney Waldhoff" <[EMAIL PROTECTED]> writes:
> > > I suggest packaging the IO-related generic-utils as a > commons.io
> > component, the lang-related utils as a > commons.lang component,
> > etc. > > Otherwise we have >
> > org.apache.commons.util.top-level-jdk-pkg... > for every class. And
> > that is supposed to *scale*?
>
> >
> >One class a project does not make...
>
> On the contrary, jakarta-collections started as just one class.
"Just one class" does not include build scripts, extra documentation,
tests, etc. Those things, along with community, are what draw the
line between a project and a class. It's like the difference between
a product and a utility.
Looking at each Commons project is a product, the Util package is a
location for utilities that aren't large enough to necessitate the
overhead involved with full productization (i.e. with starting a whole
new project).
Daniel
