Github user ejono commented on the issue:
https://github.com/apache/zeppelin/pull/1787
Answering my own questions:
I still haven't found a definitive answer to whether or not Java classes
may take advantage of default parameter values defined in Scala classes, but
it's pretty apparent that you cannot do this. This means that in order to
support both Spark < 2.1.0 and Spark >= 2.1.0, we'd need to do a little more
reflection magic to support the two possible versions of the SecurityManager
constructor.
As for the link to the Jenkins CI, I found
https://travis-ci.org/apache/zeppelin. I don't at all understand though how
the new Spark 2.1.0 profile is building successfully when I've found it so easy
to reproduce this compilation error.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
