https://builds.apache.org/job/maven-jenkinsfile/job/mng-3599/3/testReport/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVMk2Test/testitUseHttpProxyForWebDAV_4/
So why is this consistently failing on windows? I think it is that we are running without --legacy-local-repository so I have kicked off another run to see but if this does let it pass then I think we have some interesting issue to digest On 11 January 2017 at 09:54, Stephen Connolly < [email protected]> wrote: > After some analysis I think this is the Wagon upgrade to 2.10 in Maven > 3.3.9 > > I have created a mng-3599 branch in maven-integration-tests with my > proposed fix (namely deactivate the old test from 3.3.9 onwards and > duplicate with a new test for 3.3.9 onwards > > I have committed a throw-away branch in maven-core called mng-3599 with > the Jenkinsfile pointing at the mng-3599 integration tests... > > Let's see if that fixes our test for us: https://builds.apache.org/ > job/maven-jenkinsfile/job/mng-3599/ >
