Then we should use ranges to disable for newer Maven and create a new test
with a range enabling for the new mavens

On Wed 4 Jan 2017 at 19:46, Michael Osipov <micha...@apache.org> wrote:

> Am 2017-01-04 um 20:27 schrieb Stephen Connolly:
>
> > perhaps, but we need to be careful about changing ITs
>
>
>
> This being true, but having tests rely on a very old extension version
>
> does not reflect reality. Consider that the Wagon version in Maven is
>
> 2.10 but the extension in <build> 2.0. Looks awkward to me.
>
>
>
> > On 4 January 2017 at 19:22, Michael Osipov <micha...@apache.org> wrote:
>
> >
>
> >> Am 2017-01-04 um 20:16 schrieb Stephen Connolly:
>
> >>
>
> >>> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/
>
> >>> job/post-reset-master/6/testReport/junit/org.apache.
>
> >>> maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHt
>
> >>> tpProxyForWebDAV_2/
>
> >>>
>
> >>
>
> >> I have seen this somewhere else already...the Wagon version in this IT
> is
>
> >> soo old: 2.0. We should retry this IT with a new Wagon version.
>
> >>
>
> >>
>
> >>
>
> >> ---------------------------------------------------------------------
>
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>
> >> For additional commands, e-mail: dev-h...@maven.apache.org
>
> >>
>
> >>
>
> >
>
>
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
> --
Sent from my phone

Reply via email to