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 the javax.xml.ws package was not included in the web deployment when
it was built against 2.0.0-M2. I am currently building against
2.0.0-M3-SNAPSHOT.

Thanks!

On Mon, May 13, 2019 at 1:25 PM Dan Haywood <[email protected]>
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 mvn attempting to download?
>
>
> On Mon, 13 May 2019, 21:37 Brian K, <[email protected]> wrote:
>
> > https://check-host.net/check-report/a8dce74kc54
> >
> > Is this host supposed to be up?  I'm having to work in offline mode or
> set
> > maven property skip.incode-cloud-maven .
> >
> > -Brian
> >
>

Reply via email to