Hi, What I see, is that most projects are struggling to move to Java 7, Java 8 seems out of range. There are a lot of opinions and both sides of each Java version for and against. At the end of the day, it's about user feedback and committer community involvement. The projects I help on also lack manpower and maintaining more than one version is not I see folks wanting to do. For myself, I usually want to work on the current version in master/trunk and move that along. My work$ development is on Java 7 and slated to switch to Java 8 in 2016 I would guess.
Gary On Tue, Oct 27, 2015 at 9:37 AM, Oliver B. Fischer <o.b.fisc...@swe-blog.net > wrote: > Hi Vinicius, > > it is mostly to allow people which are bound (for any reason) to older JDK > versions to use our software. There is a plenty number of projects which > are not able to use newer JDK versions. I know that this is a > controversial topic I think that the majority of us would like to use all > these features. But we must not forget the people using our software in > their daily work. > > BYe, > > Oliver > > Am 27.10.15 um 16:49 schrieb Vinicius Corrêa de Almeida: > >> I analized some releases and i noticed that not using java 7 features like >> multi catch and in java 8 do not use lambda expressions and others >> features, so i came by this email to know why the developers not using >> this >> features? >> >> > -- > N Oliver B. Fischer > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > P +49 30 44793251 > M +49 178 7903538 > E o.b.fisc...@swe-blog.net > S oliver.b.fischer > J oliver.b.fisc...@jabber.org > X http://xing.to/obf > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org 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
