https://issues.apache.org/jira/browse/ZEPPELIN-5485
On Wed, Aug 11, 2021 at 9:06 AM Lior Chaga wrote:
> Gladly
>
> On Wed, Aug 11, 2021 at 9:01 AM Jeff Zhang wrote:
>
>> It seems a bug that additional configured repo doesn't work, could you
>> create a ticket for it ?
>>
>>
>> Lior Chaga 于2021
Gladly
On Wed, Aug 11, 2021 at 9:01 AM Jeff Zhang wrote:
> It seems a bug that additional configured repo doesn't work, could you
> create a ticket for it ?
>
>
> Lior Chaga 于2021年8月11日周三 下午1:50写道：
>
>> Default central repo doesn't fail, but behind VPN the zeppelin cannot
>> access central.
>>
It seems a bug that additional configured repo doesn't work, could you
create a ticket for it ?
Lior Chaga 于2021年8月11日周三 下午1:50写道：
> 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
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 z
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
