Default central repo doesn't fail, but behind VPN the zeppelin cannot
access central.
With zeppelin 0.8.2 we just configured an additional artifactory, and it
worked. For some reason (not sure why, as it uses the same
maven-resolver-api version, and I didn't notice any related code changes),
with
Hi Lior,
Thanks for the update, not sure how default central repo fails. Is it due
to you unable to access the default maven repo ?
Lior Chaga 于2021年8月11日周三 下午12:50写道：
> I found a non-patch solution, just setting
> "zeppelin.interpreter.dep.mvnRepo" to desired repo (replacing default
> central
I found a non-patch solution, just setting
"zeppelin.interpreter.dep.mvnRepo" to desired repo (replacing default
central repo)
But IMO there's still a bug (if someone simply cannot replace default repo
and have to add one)
On Tue, Aug 10, 2021 at 10:29 AM Lior Chaga wrote:
> I'm facing an issue
done
Quintin Becker 于2021年8月10日周二 下午4:30写道：
> Hi,
>
> could you please add me to your Slack-Channel ?
>
>
>
> Thanks
>
>
>
> Quintin
>
--
Best Regards
Jeff Zhang
Hi,
could you please add me to your Slack-Channel ?
Thanks
Quintin
I'm facing an issue loading repositories from the settings file.
Zeppelin uses gson to load the saved repositories, and as RemoteRepository
doesn't have a setter for protocol, it instantiates a RemoteRepository with
null protocol (not going through the Builder which resolves the protocol
from the
