Does the project *need* to use any Java7 features? Is it working OK now with Java 6 as the minimum?
If the answers are No and Yes then moving to Java 7 seems to me to be unnecessary for the initial release. On 7 June 2016 at 16:49, Marcelo Vanzin <van...@cloudera.com> wrote: > I thought there was a discussion after the project was set up to move to Java > 7? > > That being said I see that the pom still defines 1.6 as the target... > > On Mon, Jun 6, 2016 at 7:18 PM, Gary Gregory <garydgreg...@gmail.com> wrote: >> Are we really starting a new component on a dead platform like Java 6? >> >> Gary >> >> -- >> 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 > > > > -- > Marcelo > > --------------------------------------------------------------------- > 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
