18:23
> To: users@isis.apache.org
> Subject: Re: repo.incode.cloud down
>
> Maven was checking this repository before the others, so the build took a
> long time while it timed out for every artifact. It was faster when I set
> the `skip.incode-cloud-maven` property. I'm not sure wh
Unsubscribe
-Original Message-
From: Brian K
Sent: 14 May 2019 18:23
To: users@isis.apache.org
Subject: Re: repo.incode.cloud down
Maven was checking this repository before the others, so the build took a long
time while it timed out for every artifact. It was faster when I set the
Maven was checking this repository before the others, so the build took a
long time while it timed out for every artifact. It was faster when I set
the `skip.incode-cloud-maven` property. I'm not sure what artifacts are
lacking when I get the latest from the other repositories. I did notice
that
Thank you this information. I was wondering of the same thing.
Thanks,
Jayesh
On Tue, May 14, 2019, 02:55 Dan Haywood
wrote:
> Apologies, I'm in the process of recommissioning it.
> In the meantime, we have an alternative, repo.incode.work, you might want
> to try that.
>
> Which artifacts is m
Apologies, I'm in the process of recommissioning it.
In the meantime, we have an alternative, repo.incode.work, you might want
to try that.
Which artifacts is mvn attempting to download?
On Mon, 13 May 2019, 21:37 Brian K, wrote:
> https://check-host.net/check-report/a8dce74kc54
>
> Is this ho
