Hi Rick, I’m glad I’m not the only one suffering from this☺.
No, I haven’t filed an issue yet but I have just added some details to the feature request at https://issues.apache.org/jira/browse/ZEPPELIN-169, asking for a feasible workaround. I still don’t have a solution and am currently looking to see how I can hack the zeppelin-daemon.sh script on my box to call the addJarInDir function for each directory under my wisp’s lib_managed folder. However this is going to be painful because there are many folders with jars under there; I don’t know which ones are actually required dependencies (all of them?!)… I’m open to better suggestions. Unfortunately I am new to Scala so I don’t even know what ‘implicit default’ means, if indeed you’re referring to Scala! All I know is that the dependency-resolving code at https://github.com/apache/incubator-zeppelin/blob/v0.5.0/spark/src/main/java/org/apache/zeppelin/spark/dep/DependencyResolver.java could potentially call http://sonatype.github.io/sonatype-aether/apidocs/org/sonatype/aether/repository/RemoteRepository.html#setProxy%28org.sonatype.aether.repository.Proxy%29 . Maybe this is what Jeremy Subitil was implying at https://issues.apache.org/jira/browse/ZEPPELIN-169?focusedCommentId=14628118&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14628118 . If you have failing unit tests then it probably makes sense for you to raise an issue, please. Then I can always add to it. Thanks! It would be fantastic if Zeppelin could be used behind a corporate firewall☺. Lucas. From: Rick Moritz [mailto:rah...@gmail.com] Sent: 21 September 2015 15:19 To: users@zeppelin.incubator.apache.org Cc: Partridge, Lucas (GE Aviation) Subject: RE: Can't load a dependency (because I'm behind a proxy?) Hello Lucas, hello list, hopefully this message will thread properly. This problem can actually be reproduced by the corresponding unit tests - at least on my "disconnected" system, the corresponding tests for the SparkInterpreter fail in exactly the same way as your code does. This is also an issue for me, since I will probably have to get those tests to pass, in order to deploy Zeppelin on our production system. Since this actually fails unit tests, I think creating a corresponding issue is a logical next step. I'm currently looking at the code of the test to figure out which component is responsible for directing the dependency lookup to the target, and how this can be overridden, but there's probably some implicit default in use, which makes figuring the root out slightly more tricky. Have you had a look at where this could be overridden yet? Filed an issue already? Unless we get some Progress going in this thread, we should start the usual procedures... Thanks and Best, Rick
