I've hit this before, where Javadoc for 1.8 is much more strict than 1.7.
I think we should definitely use Java 1.7 for the release if we used it for
the previous releases in the 2.1 line. We don't want to break java 1.7
users in a patch release.
rb
On Fri, Apr 14, 2017 at 5:21 PM, Holden Karau
Ok and with a bit more digging between RC2 and RC3 we apparently switched
which JVM we are building the docs with.
The relevant side by side diff of the build logs (
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Release/job/spark-release-docs/60/consoleFull
https://amplab.cs.berkeley.edu/je
At first glance the error seems similar to one Pedro Rodriguez ran into
during 2.0, so I'm looping Pedor in if they happen to have any insight into
what was the cause last time.
On Fri, Apr 14, 2017 at 4:40 PM, Holden Karau wrote:
> Sure, let me dig into it :)
>
> On Fri, Apr 14, 2017 at 4:21 PM
Sure, let me dig into it :)
On Fri, Apr 14, 2017 at 4:21 PM, Michael Armbrust
wrote:
> Have time to figure out why the doc build failed?
> https://amplab.cs.berkeley.edu/jenkins/view/Spark%
> 20Release/job/spark-release-docs/60/console
>
> On Thu, Apr 13, 2017 at 9:39 PM, Holden Karau
> wrote:
Have time to figure out why the doc build failed?
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Release/job/spark-release-docs/60/console
On Thu, Apr 13, 2017 at 9:39 PM, Holden Karau wrote:
> If it would help I'd be more than happy to look at kicking off the
> packaging for RC3 since I'v
https://issues.apache.org/jira/browse/SPARK-12717
This bug is in Spark since 1.6.0.
Any chance to get this fixed ?
M.
2017-04-14 6:39 GMT+02:00 Holden Karau :
> If it would help I'd be more than happy to look at kicking off the packaging
> for RC3 since I'v been poking around in Jenkins a bit (f