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 change the specification of Maven which means that existing tests are not valid for newer versions of Maven... again they should be handled as RTC Adding new tests should be CTR That is my opinion. Jason and Robert also mostly agree with this principle... so while not put to a vote of committers (which is what would be required to make it policy - doesn't affect board delegated responsibilities so no need for PMC quorum) it is probably good enough to serve as a convention to follow - Stephen On Wed 4 Jan 2017 at 20:42, Michael Osipov <micha...@apache.org> wrote: > 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 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 > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
