New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ZEPPELIN-4583] Fix artifact resolving issues #3620
Conversation
Thanks for the fix @rimolive |
Yes, I think. The code is a bit messed in my local repo, but I'll remove this file. |
Would love to see this get in. I work with a 3rd party interpreter for Solr called zeppelin-solr, and this bug blocks us from installing it anywhere. Been a big pain for our team. Actually, now that I think of it, even when this gets merged we would have to drop a jar into our Zeppelin install or wait for a whole new release since the URL here is hardcoded in Java-land. Do you guys know of any workaround in the interim? |
@gerlowskija The only workaround I found is to apply these changes in a local repo and build zeppelin-interpreter code. Unfortunately, this change affect Java classes that must be compiled. If you are using zeppelin 0.8.2, don't forget that |
327f977
to
21aa634
Compare
@rimolive No other changes besides |
ping @rimolive |
I'm still looking at it. Something strange has happened. |
31c6093
to
21aa634
Compare
21aa634
to
e14a8df
Compare
@zjffdu I think someone already made the changes in Booter.java to use https, which makes this PR useless. I'm going to close it but looking forward for other ways to contribute with the project. |
Thanks @rimolive for the investigation. |
What is this PR for?
Fixes the problem with install-interpreter script when it tries to resolve Maven artifacts in sonatype, in which only accepts https connections recently.
What type of PR is it?
Bug Fix
What is the Jira issue?
How should this be tested?