I'm with Hen on this one. Core is coming, but not quite yet. [util] is a diverse set of useful classes that don't quite make a releasable jar. Maybe they will one day, maybe it will all be folded into [lang]. Its still not the right time to say IMHO.
Actually, the real task is to examine each of the classes, tidy up the files, licences, formatting and tests before they go anywhere. Having said that, I'd prefer to see [io] get promoted first - its closer to promotion and better defined. Stephen > from: Jeff Varszegi <[EMAIL PROTECTED]> > You're absolutely right. > > --- Ola Berg <[EMAIL PROTECTED]> wrote: > > A commons core component has been discussed before. Seems like lang, util, >collection, io and > > some more are justified there, since they cover broad aspects of java programming. >This is > > something that we (according to the discussions) seems to see in the future. > > > > But given the closeness between them, isn't it already now justified to manage >both the > > o.a.c.lang and the o.a.c.util package in the thought of basic commons component >named [core]? > > They are both small and very very very basic. Handling them as two >jars/subprojects/downloads > > seems to be so much work for so little achieved. > > > > I say: let's marry them together. What do you think? > > > > /O > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus � Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
