Maybe just test if things change when running those ITs multiple times
with Maven 3.0.5 instead of 3.3.9.
Am 01/05/17 um 02:37 schrieb Christian Schulte:
> Am 01/04/17 um 20:16 schrieb Stephen Connolly:
>> https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testRepor
Am 01/04/17 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/testitUseHttpProxyForWebDAV_2/
>
> Seems to fail at random on Windows...
>
It may be a
We don't delete them. We can mark them as skipped using the range
facilities of the integration tests
Integration tests should be mostly append only.
There are some rare cases were an existing test needs modification. Those
should be handled as RTC
There are more cases where we may decide to cha
Sounds reasonable. This applies to a lot of tests. There are also a
bunch of tests which apply to Maven 2.x only. I see no reason to keep
them around.
Michael
Am 2017-01-04 um 21:26 schrieb Stephen Connolly:
Then we should use ranges to disable for newer Maven and create a new test
with a ran
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 wrote:
> Am 2017-01-04 um 20:27 schrieb Stephen Connolly:
>
> > perhaps, but we need to be careful about changing ITs
>
>
>
> This being
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 2.0. Looks awkward to
perhaps, but we need to be careful about changing ITs
On 4 January 2017 at 19:22, Michael Osipov 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/MavenITm
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/testitUseHttpProxyForWebDAV_2/
I have seen this somewhere else already...the Wagon ver
https://builds.apache.org/view/Maven/job/maven-jenkinsfile/job/post-reset-master/6/testReport/junit/org.apache.maven.it/MavenITmng3599useHttpProxyForWebDAVTest/testitUseHttpProxyForWebDAV_2/
Seems to fail at random on Windows...
