+1 for java 8 as the default. We don't want this brand new thing looking old because it's based on an older JVM. Java 8 adoption is also really up there, per[1].
For components you're stuffing into app servers, it's a little harder, since you do have to be Java 7 compliant for EE 7 (you can go lower, but not higher). [1]: http://jaxenter.com/java-2-111936.html On Fri Nov 28 2014 at 12:27:40 PM Andres Almiray <[email protected]> wrote: > AFAIK JDK8 should be the baseline as it can *force* the hand for adoption, > yes, this is desired. > Otherwise we'll be stuck in JDK7 or even worse, JDK6. > > JDK8 also opens the door for additional design features such as > > - static methods on interfaces > - default methods > - repeatable annotations > - usage of Optional > > Cheers, > Andres > > ------------------------------------------- > Java Champion; Groovy Enthusiast > http://jroller.com/aalmiray > http://www.linkedin.com/in/aalmiray > -- > What goes up, must come down. Ask any system administrator. > There are 10 types of people in the world: Those who understand binary, and > those who don't. > To understand recursion, we must first understand recursion. > > On Fri, Nov 28, 2014 at 6:19 PM, Romain Manni-Bucau <[email protected] > > > wrote: > > > Hi guys, > > > > just checkouted sources and seems project targets java 8. Don't we > > want to support java 7 as well? Otherwise it can be a blocker for > > adaption I think > > > > > > Romain Manni-Bucau > > @rmannibucau > > http://www.tomitribe.com > > http://rmannibucau.wordpress.com > > https://github.com/rmannibucau > > >
