Perhaps we should do the following in trunk: 1) Generify (I know, it's not a word and it is funny that my spellchecker suggests 'gentrify')) everything and keep backwards compatibility (this has started) 2) Re-implement using Java 5 APIs where appropriate. For example, if we catch and re-throw an exception, make sure we pass the cause up the chain. 3) See what it all looks like 4) Discuss what old style APIs to remove if any. For example: Do we keep foo(Type[]) when we now have foo(List<Type>)) or foo(Iterable<Type>)
Gary > -----Original Message----- > From: Torsten Curdt [mailto:[EMAIL PROTECTED] > Sent: Monday, February 11, 2008 10:34 AM > To: Jakarta Commons Developers List > Subject: Re: [io] 2.0 Moving to minimum of JDK 1.5 > > >>> I still don't see the need to overhaul the entire API. > >> > >> And I don't see the point why we shouldn't. Going from from java 1.4 > >> -> 1.5 usually means a bit overhaul. > > > > Perhaps usually, but for Commons IO? > > The question was - why not? We are running around in circles here. > > > I see only a few isolated candidates for Java 5 improvements > > <snip/> > > Counting that's already 4 :) > > > Do such isolated changes justify changing the entire API? Or do you > > have some other major changes in mind? > > Hell, it's a new version and no one would be required to upgrade. And > upgrading would still be easy. So why not get rid of some cruft. > > Could we maybe just settle on doing the changes on a branch first and > then discuss compatibility and a possible merge? > > cheers > -- > Torsten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
