@Sean, I'm using Java 8 but don't see these errors until I manually build
the API docs. Hence I think dropping Java 7 support may not help.
Right now we don't build docs in most of builds as building docs takes a
long time (e.g.,
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-docs/2889/
old Xin <r...@databricks.com<mailto:r...@databricks.com>>
Sent: Tuesday, February 7, 2017 4:48 AM
Subject: Re: PSA: Java 8 unidoc build
To: Sean Owen <so...@cloudera.com<mailto:so...@cloudera.com>>
Cc: Josh Rosen <joshro...@databricks.com<mailto:joshro..
I don't know if this would help but I think we can also officially stop
supporting Java 7 ...
On Tue, Feb 7, 2017 at 1:06 PM, Sean Owen wrote:
> I believe that if we ran the Jenkins builds with Java 8 we would catch
> these? this doesn't require dropping Java 7 support or
I believe that if we ran the Jenkins builds with Java 8 we would catch
these? this doesn't require dropping Java 7 support or anything.
@joshrosen I know we are just now talking about modifying the Jenkins jobs
to remove old Hadoop configs. Is it possible to change the master jobs to
use Java 8?
(One more.. https://github.com/apache/spark/pull/15999 this describes some
more cases that might easily be mistaken)
On 7 Feb 2017 9:21 a.m., "Hyukjin Kwon" wrote:
> Oh, Joseph, thanks. It is nice to inform this in dev mailing list.
>
> Let me please leave another PR to
Oh, Joseph, thanks. It is nice to inform this in dev mailing list.
Let me please leave another PR to refer,
https://github.com/apache/spark/pull/16013
and the JIRA you kindly opened,
https://issues.apache.org/jira/browse/SPARK-18692
On 7 Feb 2017 9:13 a.m., "Joseph Bradley"
Public service announcement: Our doc build has worked with Java 8 for brief
time periods, but new changes keep breaking the Java 8 unidoc build.
Please be aware of this, and try to test doc changes with Java 8! In
general, it is stricter than Java 7 for docs.
A shout out to @HyukjinKwon and