Failing Builds on Travis

[Robert Metzger]

Hi,

looking at the last builds on Travis, you'll notice that our builds are in
a pretty bad state: https://travis-ci.org/apache/flink/builds.
It seems that the last 15 builds on master all failed.

These are the errors I saw + their status:
- Deadlock during cache up/download: I asked travis and they suggested a
workaround that I'm currently testing (MALLOC_ARENA=2, in master)
- issues opening zip files: The problem there is that some jars in the
cache seem to be corrupt. I asked ASF Infra to delete all caches, they did
it already, so the problem should be resolved.
- Maven failing on the java6 builds. The issue is that Travis updated their
build environment (April update [1]), which included a version upgrade of
Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting Java
6 anymore [2].
It seems that travis is rolling back the April environment updates [3] so
the issue will probably disappear for a few days until they fixed their
environment update.
We can resolve the issue by two ways a) drop Java6 support, b) manually
install maven on travis (its a matter of 1-2hrs).
- The third build on travis (hadoop200-alpha) is failing due to some Flink
tests: https://travis-ci.org/apache/flink/jobs/60335907
It would be good if somebody who worked on this recently could take a
closer look.


Please let me know how you want to fix the Java6/Maven issue!
a) Drop Java 6 support for Flink
b) Use an older Maven version for now.

I'm in favor of option b) because the community recently decided to keep
Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
in April 2015)


Robert

[1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
[2] https://issues.apache.org/jira/browse/MNG-5780
[3] https://twitter.com/traviscistatus/status/592902357144498176
[4]
http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29

[mxm]

Hi Robert,

Thanks for investigating the Travis build issues. I'm very much in favor
for dropping Java 6. It's deprecated. All major Linux distributions are
shipping at least Java 7. It's a rare use case that requires a lot of
effort for us to maintain backwards compatibility.

I don't recall the discussion but if we really decided to keep Java 6, then
I guess we have to install a custom Maven version on Travis.

Best,
Max

On Tue, Apr 28, 2015 at 1:34 PM, Robert Metzger <[hidden email]> wrote:

> Hi,
>
> looking at the last builds on Travis, you'll notice that our builds are in
> a pretty bad state: https://travis-ci.org/apache/flink/builds.
> It seems that the last 15 builds on master all failed.
>
> These are the errors I saw + their status:
> - Deadlock during cache up/download: I asked travis and they suggested a
> workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> - issues opening zip files: The problem there is that some jars in the
> cache seem to be corrupt. I asked ASF Infra to delete all caches, they did
> it already, so the problem should be resolved.
> - Maven failing on the java6 builds. The issue is that Travis updated their
> build environment (April update [1]), which included a version upgrade of
> Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting Java
> 6 anymore [2].
> It seems that travis is rolling back the April environment updates [3] so
> the issue will probably disappear for a few days until they fixed their
> environment update.
> We can resolve the issue by two ways a) drop Java6 support, b) manually
> install maven on travis (its a matter of 1-2hrs).
> - The third build on travis (hadoop200-alpha) is failing due to some Flink
> tests: https://travis-ci.org/apache/flink/jobs/60335907
> It would be good if somebody who worked on this recently could take a
> closer look.
>
>
> Please let me know how you want to fix the Java6/Maven issue!
> a) Drop Java 6 support for Flink
> b) Use an older Maven version for now.
>
> I'm in favor of option b) because the community recently decided to keep
> Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
> in April 2015)
>
>
> Robert
>
> [1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> [2] https://issues.apache.org/jira/browse/MNG-5780
> [3] https://twitter.com/traviscistatus/status/592902357144498176
> [4]
>
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29
>

[Robert Metzger]

I looked a bit closer into the Maven issue, maybe Travis is going to
provide a compatible Maven version for the Java6 build environment:
https://github.com/travis-ci/travis-ci/issues/3778

On Tue, Apr 28, 2015 at 1:49 PM, Maximilian Michels <[hidden email]> wrote:

> Hi Robert,
>
> Thanks for investigating the Travis build issues. I'm very much in favor
> for dropping Java 6. It's deprecated. All major Linux distributions are
> shipping at least Java 7. It's a rare use case that requires a lot of
> effort for us to maintain backwards compatibility.
>
> I don't recall the discussion but if we really decided to keep Java 6, then
> I guess we have to install a custom Maven version on Travis.
>
> Best,
> Max
>
> On Tue, Apr 28, 2015 at 1:34 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > Hi,
> >
> > looking at the last builds on Travis, you'll notice that our builds are
> in
> > a pretty bad state: https://travis-ci.org/apache/flink/builds.
> > It seems that the last 15 builds on master all failed.
> >
> > These are the errors I saw + their status:
> > - Deadlock during cache up/download: I asked travis and they suggested a
> > workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> > - issues opening zip files: The problem there is that some jars in the
> > cache seem to be corrupt. I asked ASF Infra to delete all caches, they
> did
> > it already, so the problem should be resolved.
> > - Maven failing on the java6 builds. The issue is that Travis updated
> their
> > build environment (April update [1]), which included a version upgrade of
> > Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting
> Java
> > 6 anymore [2].
> > It seems that travis is rolling back the April environment updates [3] so
> > the issue will probably disappear for a few days until they fixed their
> > environment update.
> > We can resolve the issue by two ways a) drop Java6 support, b) manually
> > install maven on travis (its a matter of 1-2hrs).
> > - The third build on travis (hadoop200-alpha) is failing due to some
> Flink
> > tests: https://travis-ci.org/apache/flink/jobs/60335907
> > It would be good if somebody who worked on this recently could take a
> > closer look.
> >
> >
> > Please let me know how you want to fix the Java6/Maven issue!
> > a) Drop Java 6 support for Flink
> > b) Use an older Maven version for now.
> >
> > I'm in favor of option b) because the community recently decided to keep
> > Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
> > in April 2015)
> >
> >
> > Robert
> >
> > [1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> > [2] https://issues.apache.org/jira/browse/MNG-5780
> > [3] https://twitter.com/traviscistatus/status/592902357144498176
> > [4]
> >
> >
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29
> >
>

[Ufuk Celebi-2]

On 28 Apr 2015, at 13:49, Maximilian Michels <[hidden email]> wrote:

> Hi Robert,
>
> Thanks for investigating the Travis build issues. I'm very much in favor
> for dropping Java 6. It's deprecated. All major Linux distributions are
> shipping at least Java 7. It's a rare use case that requires a lot of
> effort for us to maintain backwards compatibility.
>
> I don't recall the discussion but if we really decided to keep Java 6, then
> I guess we have to install a custom Maven version on Travis.

There was a discussion ~6 months ago: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Bump-the-minimum-Java-requirement-to-Java-7-for-Flink-td2243.html#a2249

Result was to not drop support for it. I'm not sure if anything has changed (with regards to the arguments made). You can start a new discussion if you think we should consider dropping support. In any case, let's not mix it up with the discussion here.

– Ufuk

[Till Rohrmann]

Concerning the failed builds in the hadoop2.0.0-alpha profile I see a lot
of

07:47:57,927 ERROR akka.actor.ActorSystemImpl
     - Uncaught fatal error from thread
[flink-akka.remote.default-remote-dispatcher-7] shutting down ActorSystem
[flink]
java.lang.VerifyError: (class:
org/jboss/netty/channel/socket/nio/NioWorkerPool, method: createWorker
signature:
(Ljava/util/concurrent/Executor;)Lorg/jboss/netty/channel/socket/nio/AbstractNioWorker;)
Wrong return type in function
at
akka.remote.transport.netty.NettyTransport.<init>(NettyTransport.scala:283)
at
akka.remote.transport.netty.NettyTransport.<init>(NettyTransport.scala:240)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at
akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$2.apply(DynamicAccess.scala:78)
at scala.util.Try$.apply(Try.scala:161)
at
akka.actor.ReflectiveDynamicAccess.createInstanceFor(DynamicAccess.scala:73)
at
akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$3.apply(DynamicAccess.scala:84)
at
akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$3.apply(DynamicAccess.scala:84)
at scala.util.Success.flatMap(Try.scala:200)
at
akka.actor.ReflectiveDynamicAccess.createInstanceFor(DynamicAccess.scala:84)
at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:692)
at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:684)
at
scala.collection.TraversableLike$WithFilter$$anonfun$map$2.apply(TraversableLike.scala:722)
at scala.collection.Iterator$class.foreach(Iterator.scala:727)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
at
scala.collection.TraversableLike$WithFilter.map(TraversableLike.scala:721)
at
akka.remote.EndpointManager.akka$remote$EndpointManager$$listens(Remoting.scala:684)
at
akka.remote.EndpointManager$$anonfun$receive$2.applyOrElse(Remoting.scala:492)
at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
at akka.remote.EndpointManager.aroundReceive(Remoting.scala:395)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
at akka.actor.ActorCell.invoke(ActorCell.scala:487)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:254)
at akka.dispatch.Mailbox.run(Mailbox.scala:221)
at akka.dispatch.Mailbox.exec(Mailbox.scala:231)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at
scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

in the logs. This does not look right and indicates a version conflict of
Netty. Netty 4.0 does not longer have a NioWorkerPool. I suspect that we
have multiple Netty jars in the class path. This might be related to the
other problems we're currently having with Travis.

On Tue, Apr 28, 2015 at 2:53 PM, Ufuk Celebi <[hidden email]> wrote:

>
> On 28 Apr 2015, at 13:49, Maximilian Michels <[hidden email]> wrote:
>
> > Hi Robert,
> >
> > Thanks for investigating the Travis build issues. I'm very much in favor
> > for dropping Java 6. It's deprecated. All major Linux distributions are
> > shipping at least Java 7. It's a rare use case that requires a lot of
> > effort for us to maintain backwards compatibility.
> >
> > I don't recall the discussion but if we really decided to keep Java 6,
> then
> > I guess we have to install a custom Maven version on Travis.
>
> There was a discussion ~6 months ago:
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Bump-the-minimum-Java-requirement-to-Java-7-for-Flink-td2243.html#a2249
>
> Result was to not drop support for it. I'm not sure if anything has
> changed (with regards to the arguments made). You can start a new
> discussion if you think we should consider dropping support. In any case,
> let's not mix it up with the discussion here.
>
> – Ufuk

[Henry Saputra]

For now, the right way to use older Maven version BUT I would
recommend, similar to Spargel, make 0.9 be last release for Java6.

It is already end of life and more and more developers start flocking
to Java7 and Java8.


- Henry

On Tue, Apr 28, 2015 at 4:34 AM, Robert Metzger <[hidden email]> wrote:

> Hi,
>
> looking at the last builds on Travis, you'll notice that our builds are in
> a pretty bad state: https://travis-ci.org/apache/flink/builds.
> It seems that the last 15 builds on master all failed.
>
> These are the errors I saw + their status:
> - Deadlock during cache up/download: I asked travis and they suggested a
> workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> - issues opening zip files: The problem there is that some jars in the
> cache seem to be corrupt. I asked ASF Infra to delete all caches, they did
> it already, so the problem should be resolved.
> - Maven failing on the java6 builds. The issue is that Travis updated their
> build environment (April update [1]), which included a version upgrade of
> Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting Java
> 6 anymore [2].
> It seems that travis is rolling back the April environment updates [3] so
> the issue will probably disappear for a few days until they fixed their
> environment update.
> We can resolve the issue by two ways a) drop Java6 support, b) manually
> install maven on travis (its a matter of 1-2hrs).
> - The third build on travis (hadoop200-alpha) is failing due to some Flink
> tests: https://travis-ci.org/apache/flink/jobs/60335907
> It would be good if somebody who worked on this recently could take a
> closer look.
>
>
> Please let me know how you want to fix the Java6/Maven issue!
> a) Drop Java 6 support for Flink
> b) Use an older Maven version for now.
>
> I'm in favor of option b) because the community recently decided to keep
> Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
> in April 2015)
>
>
> Robert
>
> [1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> [2] https://issues.apache.org/jira/browse/MNG-5780
> [3] https://twitter.com/traviscistatus/status/592902357144498176
> [4]
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29

[Stephan Ewen]

Agree, I would also like to drop Java 6 after 0.9.

On Tue, Apr 28, 2015 at 7:19 PM, Henry Saputra <[hidden email]>
wrote:

> For now, the right way to use older Maven version BUT I would
> recommend, similar to Spargel, make 0.9 be last release for Java6.
>
> It is already end of life and more and more developers start flocking
> to Java7 and Java8.
>
>
> - Henry
>
> On Tue, Apr 28, 2015 at 4:34 AM, Robert Metzger <[hidden email]>
> wrote:
> > Hi,
> >
> > looking at the last builds on Travis, you'll notice that our builds are
> in
> > a pretty bad state: https://travis-ci.org/apache/flink/builds.
> > It seems that the last 15 builds on master all failed.
> >
> > These are the errors I saw + their status:
> > - Deadlock during cache up/download: I asked travis and they suggested a
> > workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> > - issues opening zip files: The problem there is that some jars in the
> > cache seem to be corrupt. I asked ASF Infra to delete all caches, they
> did
> > it already, so the problem should be resolved.
> > - Maven failing on the java6 builds. The issue is that Travis updated
> their
> > build environment (April update [1]), which included a version upgrade of
> > Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting
> Java
> > 6 anymore [2].
> > It seems that travis is rolling back the April environment updates [3] so
> > the issue will probably disappear for a few days until they fixed their
> > environment update.
> > We can resolve the issue by two ways a) drop Java6 support, b) manually
> > install maven on travis (its a matter of 1-2hrs).
> > - The third build on travis (hadoop200-alpha) is failing due to some
> Flink
> > tests: https://travis-ci.org/apache/flink/jobs/60335907
> > It would be good if somebody who worked on this recently could take a
> > closer look.
> >
> >
> > Please let me know how you want to fix the Java6/Maven issue!
> > a) Drop Java 6 support for Flink
> > b) Use an older Maven version for now.
> >
> > I'm in favor of option b) because the community recently decided to keep
> > Java6 support. (Fun fact: Java 7 reached its end of support lifecycle [4]
> > in April 2015)
> >
> >
> > Robert
> >
> > [1] http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> > [2] https://issues.apache.org/jira/browse/MNG-5780
> > [3] https://twitter.com/traviscistatus/status/592902357144498176
> > [4]
> >
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29
>

[mxm]

Bringing this up again because of a recently discovered issue:
https://issues.apache.org/jira/browse/FLINK-2235

Flink 0.9.0 will still support Java 6. Just wanted to clarify again that we
drop support for Java 6 for any further major releases. Do we have a
consensus?

On Tue, Apr 28, 2015 at 7:26 PM, Stephan Ewen <[hidden email]> wrote:

> Agree, I would also like to drop Java 6 after 0.9.
>
> On Tue, Apr 28, 2015 at 7:19 PM, Henry Saputra <[hidden email]>
> wrote:
>
> > For now, the right way to use older Maven version BUT I would
> > recommend, similar to Spargel, make 0.9 be last release for Java6.
> >
> > It is already end of life and more and more developers start flocking
> > to Java7 and Java8.
> >
> >
> > - Henry
> >
> > On Tue, Apr 28, 2015 at 4:34 AM, Robert Metzger <[hidden email]>
> > wrote:
> > > Hi,
> > >
> > > looking at the last builds on Travis, you'll notice that our builds are
> > in
> > > a pretty bad state: https://travis-ci.org/apache/flink/builds.
> > > It seems that the last 15 builds on master all failed.
> > >
> > > These are the errors I saw + their status:
> > > - Deadlock during cache up/download: I asked travis and they suggested
> a
> > > workaround that I'm currently testing (MALLOC_ARENA=2, in master)
> > > - issues opening zip files: The problem there is that some jars in the
> > > cache seem to be corrupt. I asked ASF Infra to delete all caches, they
> > did
> > > it already, so the problem should be resolved.
> > > - Maven failing on the java6 builds. The issue is that Travis updated
> > their
> > > build environment (April update [1]), which included a version upgrade
> of
> > > Maven from 3.2.5 to 3.3.1. As per Maven 3.3.1, they are not supporting
> > Java
> > > 6 anymore [2].
> > > It seems that travis is rolling back the April environment updates [3]
> so
> > > the issue will probably disappear for a few days until they fixed their
> > > environment update.
> > > We can resolve the issue by two ways a) drop Java6 support, b) manually
> > > install maven on travis (its a matter of 1-2hrs).
> > > - The third build on travis (hadoop200-alpha) is failing due to some
> > Flink
> > > tests: https://travis-ci.org/apache/flink/jobs/60335907
> > > It would be good if somebody who worked on this recently could take a
> > > closer look.
> > >
> > >
> > > Please let me know how you want to fix the Java6/Maven issue!
> > > a) Drop Java 6 support for Flink
> > > b) Use an older Maven version for now.
> > >
> > > I'm in favor of option b) because the community recently decided to
> keep
> > > Java6 support. (Fun fact: Java 7 reached its end of support lifecycle
> [4]
> > > in April 2015)
> > >
> > >
> > > Robert
> > >
> > > [1]
> http://docs.travis-ci.com/user/build-environment-updates/2015-04-09/
> > > [2] https://issues.apache.org/jira/browse/MNG-5780
> > > [3] https://twitter.com/traviscistatus/status/592902357144498176
> > > [4]
> > >
> >
> http://en.wikipedia.org/wiki/Java_version_history#Java_SE_7_.28July_28.2C_2011.29
> >
>

[Ufuk Celebi-2]

On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]> wrote:

> Bringing this up again because of a recently discovered issue:
> https://issues.apache.org/jira/browse/FLINK-2235
>
> Flink 0.9.0 will still support Java 6. Just wanted to clarify again that we
> drop support for Java 6 for any further major releases. Do we have a
> consensus?

+1

[Matthias J. Sax]

+1

On 06/19/2015 10:35 AM, Ufuk Celebi wrote:

>
> On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]> wrote:
>
>> Bringing this up again because of a recently discovered issue:
>> https://issues.apache.org/jira/browse/FLINK-2235
>>
>> Flink 0.9.0 will still support Java 6. Just wanted to clarify again that we
>> drop support for Java 6 for any further major releases. Do we have a
>> consensus?
>
> +1
>

[Stephan Ewen]

+1

On Fri, Jun 19, 2015 at 10:48 AM, Matthias J. Sax <
[hidden email]> wrote:

> +1
>
> On 06/19/2015 10:35 AM, Ufuk Celebi wrote:
> >
> > On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]> wrote:
> >
> >> Bringing this up again because of a recently discovered issue:
> >> https://issues.apache.org/jira/browse/FLINK-2235
> >>
> >> Flink 0.9.0 will still support Java 6. Just wanted to clarify again
> that we
> >> drop support for Java 6 for any further major releases. Do we have a
> >> consensus?
> >
> > +1
> >
>
>

[Fabian Hueske-2]

+1

2015-06-22 17:44 GMT+02:00 Stephan Ewen <[hidden email]>:

> +1
>
> On Fri, Jun 19, 2015 at 10:48 AM, Matthias J. Sax <
> [hidden email]> wrote:
>
> > +1
> >
> > On 06/19/2015 10:35 AM, Ufuk Celebi wrote:
> > >
> > > On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]> wrote:
> > >
> > >> Bringing this up again because of a recently discovered issue:
> > >> https://issues.apache.org/jira/browse/FLINK-2235
> > >>
> > >> Flink 0.9.0 will still support Java 6. Just wanted to clarify again
> > that we
> > >> drop support for Java 6 for any further major releases. Do we have a
> > >> consensus?
> > >
> > > +1
> > >
> >
> >
>

[Robert Metzger]

+1



On Tue, Jun 23, 2015 at 11:31 AM, Fabian Hueske <[hidden email]> wrote:

> +1
>
> 2015-06-22 17:44 GMT+02:00 Stephan Ewen <[hidden email]>:
>
> > +1
> >
> > On Fri, Jun 19, 2015 at 10:48 AM, Matthias J. Sax <
> > [hidden email]> wrote:
> >
> > > +1
> > >
> > > On 06/19/2015 10:35 AM, Ufuk Celebi wrote:
> > > >
> > > > On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]> wrote:
> > > >
> > > >> Bringing this up again because of a recently discovered issue:
> > > >> https://issues.apache.org/jira/browse/FLINK-2235
> > > >>
> > > >> Flink 0.9.0 will still support Java 6. Just wanted to clarify again
> > > that we
> > > >> drop support for Java 6 for any further major releases. Do we have a
> > > >> consensus?
> > > >
> > > > +1
> > > >
> > >
> > >
> >
>

[Till Rohrmann]

+1

On Tue, Jun 23, 2015 at 3:16 PM, Robert Metzger <[hidden email]> wrote:

> +1
>
>
>
> On Tue, Jun 23, 2015 at 11:31 AM, Fabian Hueske <[hidden email]> wrote:
>
> > +1
> >
> > 2015-06-22 17:44 GMT+02:00 Stephan Ewen <[hidden email]>:
> >
> > > +1
> > >
> > > On Fri, Jun 19, 2015 at 10:48 AM, Matthias J. Sax <
> > > [hidden email]> wrote:
> > >
> > > > +1
> > > >
> > > > On 06/19/2015 10:35 AM, Ufuk Celebi wrote:
> > > > >
> > > > > On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]>
> wrote:
> > > > >
> > > > >> Bringing this up again because of a recently discovered issue:
> > > > >> https://issues.apache.org/jira/browse/FLINK-2235
> > > > >>
> > > > >> Flink 0.9.0 will still support Java 6. Just wanted to clarify
> again
> > > > that we
> > > > >> drop support for Java 6 for any further major releases. Do we
> have a
> > > > >> consensus?
> > > > >
> > > > > +1
> > > > >
> > > >
> > > >
> > >
> >
>

[Robert Metzger]

I created a JIRA for this: https://issues.apache.org/jira/browse/FLINK-2307

On Wed, Jun 24, 2015 at 3:01 PM, Till Rohrmann <[hidden email]> wrote:

> +1
>
> On Tue, Jun 23, 2015 at 3:16 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > +1
> >
> >
> >
> > On Tue, Jun 23, 2015 at 11:31 AM, Fabian Hueske <[hidden email]>
> wrote:
> >
> > > +1
> > >
> > > 2015-06-22 17:44 GMT+02:00 Stephan Ewen <[hidden email]>:
> > >
> > > > +1
> > > >
> > > > On Fri, Jun 19, 2015 at 10:48 AM, Matthias J. Sax <
> > > > [hidden email]> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On 06/19/2015 10:35 AM, Ufuk Celebi wrote:
> > > > > >
> > > > > > On 19 Jun 2015, at 10:29, Maximilian Michels <[hidden email]>
> > wrote:
> > > > > >
> > > > > >> Bringing this up again because of a recently discovered issue:
> > > > > >> https://issues.apache.org/jira/browse/FLINK-2235
> > > > > >>
> > > > > >> Flink 0.9.0 will still support Java 6. Just wanted to clarify
> > again
> > > > > that we
> > > > > >> drop support for Java 6 for any further major releases. Do we
> > have a
> > > > > >> consensus?
> > > > > >
> > > > > > +1
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>