I've said it before: doocracy. If someone wants to take on the work to provide 1.5 support, they've widened the audience of the component, which should be seen as a win if it didn't cause anyone else a problem. Maybe we should have a [compatibility] component to capture these backports in a reusable way! ;-)
Matt On Mar 1, 2014 11:34 AM, "Benedikt Ritter" <[email protected]> wrote: > If it's only test code, I'm hesitant to move to Java 6. Are there > improvements for production code as well? > > Benedikt > > > 2014-03-01 17:54 GMT+01:00 Gary Gregory <[email protected]>: > > > On Sat, Mar 1, 2014 at 11:47 AM, Emmanuel Bourg <[email protected]> > wrote: > > > > > +1 to stop bothering with Java 5 for all our components. > > > > > > > +1 :) > > Gary > > > > > > > > > > Emmanuel Bourg > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > -- > > E-Mail: [email protected] | [email protected] > > Java Persistence with Hibernate, Second Edition< > > http://www.manning.com/bauer3/> > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > > Spring Batch in Action <http://www.manning.com/templier/> > > Blog: http://garygregory.wordpress.com > > Home: http://garygregory.com/ > > Tweet! http://twitter.com/GaryGregory > > > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter >
