Re: Moving to jdk7 or jdk8

I agree to enforce maven 3 but I would handle it in a separate JIRA. Meanwhile, anyone interested in reviewing the java8 upgrade? AVRO-2043 Thanks, Gabor On Fri, Jun 16, 2017 at 7:11 PM, Sean Busbey wrote: > Could we start

Re: Moving to jdk7 or jdk8

Could we start enforcing Maven 3.0.5+ as well? Right now we require 2.2.1+ and Maven 2 hit EOL in May 2014 (its last release was Nov 2009) On Fri, Jun 16, 2017 at 12:17 AM, Gabor Szadovszky wrote: > Created the JIRA AVRO-2043 >

Re: Moving to jdk7 or jdk8

Created the JIRA AVRO-2043 to track this. Feel free to add anything I've missed. On Thu, Jun 15, 2017 at 8:14 PM, Ryan Blue wrote: > Yeah, lets stick with 2.7.x instead of 3.x for now. > > I was talking about the 1.9

Re: Moving to jdk7 or jdk8

Yeah, lets stick with 2.7.x instead of 3.x for now. I was talking about the 1.9 release line for updating the JDK version. I agree we shouldn't move 1.8 or 1.7. On Thu, Jun 15, 2017 at 10:53 AM, Sean Busbey wrote: > if we're talking about for the 1.9 release line, then I'm

Re: Moving to jdk7 or jdk8

+1 for moving. I'm in favor of moving to Java 8 since Java 7 has been end of life for 2 years. https://www.infoq.com/news/2015/05/Oracle-Ends-Java-7Public-Updates rb On Wed, Jun 14, 2017 at 7:56 AM, suraj acharya wrote: > Looking through jira. I dont see a plan as such.

Moving to jdk7 or jdk8

Hi All, Are we planning to move to a newer jdk in the next major release 1.9.0? To be more precise: - Upgrading build jdk from 7 to 8? - Upgrading source/target version from 1.6 to 1.7 or 1.8? Thanks a lot, Gabor