Re: Compile for Java 1.8

Sounds good to me if possible without breaking anything :-) On 14 November 2016 at 10:57:26, Andrey Melentyev (andrey.melent...@gmail.com) wrote: > Ufuk, > > do you think it's still worth fixing the build errors and maybe adding a > Travis configuration to build and test against 1.8? Or do you

Re: Compile for Java 1.8

Ufuk, do you think it's still worth fixing the build errors and maybe adding a Travis configuration to build and test against 1.8? Or do you think that would introduce too much additional overheads? I mean without deprecating 1.7 support of course. Andrey On Mon, Nov 14, 2016 at 10:51 AM, Ufuk C

Re: Compile for Java 1.8

As far as I know, there were no concrete discussions about this yet. I would not expect it to happen this year, but maybe/probably in the course of next year. We would have to have a release where we explicitly say that this will be the last major release with 1.7 support, so users running old v

Re: Compile for Java 1.8

Thanks. Sounds weird I imagine the Flink team have a road-map to migrate to Java 1.8 On "Build From source ": "Flink requires *at least Java 7* to build. We recommend using Java 8." 2016-11-13 17:48 GMT+01:00 Andr

Re: Compile for Java 1.8

Hi Alberto, it seems that this class is not compatible with Java 8 new type inference rules, more specifically the 1.8 compiler picks a different overloaded method than 1.7. In TupleSerializer.java:112 the call to TypeSerializer.copy method in Java 7 resolves to public abstract T copy(T from, T

Compile for Java 1.8

bash> git Clone POM> 1.8 bash> java -version ==> java version "1.8.0_111" *Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project flink-core: Compilation failure[ERROR] . . . /flink1.2 _10_Nov/flink-core/src/main/java/org/apache/flink/api/ja