On 10 November 2011 14:04, Gary Gregory <garydgreg...@gmail.com> wrote: > On Nov 10, 2011, at 3:51, Emmanuel Bourg <ebo...@apache.org> wrote: > >> Le 09/11/2011 13:59, Gary Gregory a écrit : >>> +1. >>> >>> You can even make it use Java 6 as far as I'm concerned. >> >> Well I'm not sure there is enough meat in [csv] to require Java 6, but >> at least Java 5 opens a wide range of possibilities. For example I >> turned the parser into an iterable to make it usable in foreach loops. >> Also the bean mapping could be done easily by adding some annotations. >> > > Going to 6 instead 5 would be a good test of for Commons in general, > even if this specific component is not meaty enough yet.
Not sure what the benefits would be. It's already possible to compile and test components using Java 6. Requiring Java 6 even though Java 5 is sufficient for the needs of the component seems wrong, as it potentially excludes users. The move to Java 5 is different, as it brings a lot of benefits (improved memory model, concurrent, generics etc); Java 6 mainly offers extra methods and bugfixes. There are fewer reasons to require Java 6, but of course Java 5 code will run under Java 6+. Commons components should be usable by as many as possible, so should not arbitrarily require a more recent Java version than necessary. > Gary > >> Emmanuel Bourg >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
