Try to fix MavenITmng7836AlternativePomSyntaxTest

[slawekjaranowski]

No description provided.

[slawekjaranowski]

This patch make a build green https://github.com/apache/maven/actions/runs/6318762268
but not resolve a problem

[gnodet]

The fix is #308.
The problem occurred because I split some PRs. Each PR was individually passing the tests, but when both had been merged, the test from the first PR was broken by the second PR.

[gnodet]

Those should not be needed.
IIUC, this should already be fixed by apache/maven@f24266e#diff-5dbf1a803ecc13ff945a08ed3eb09149a83615e83f15320550af8e3a91976446

[slawekjaranowski]

It fix only build on GitHub teh same local repo is used for build Maven and execute IT
but on jenkins and on local host we have separate clean repo for ITs

[slawekjaranowski]

Master build is still suffer from it ... do we have any other idea - how to fix
After release alpha-8 we will can remove access to remote repo and move needed artifacts to bootstrap.

[gnodet]

Master build is still suffer from it ... do we have any other idea - how to fix After release alpha-8 we will can remove access to remote repo and move needed artifacts to bootstrap.

I still think we should run the integration tests on a locally build distribution, else there's no way we can test something depending on new code in maven. So for the time being, I would either disable the test until alpha-8 is released or build Maven snapshot locally (or disable Jenkins jobs which are the only one failing).

[slawekjaranowski]

Master build is still suffer from it ... do we have any other idea - how to fix After release alpha-8 we will can remove access to remote repo and move needed artifacts to bootstrap.

I still think we should run the integration tests on a locally build distribution, else there's no way we can test something depending on new code in maven. So for the time being, I would either disable the test until alpha-8 is released or build Maven snapshot locally (or disable Jenkins jobs which are the only one failing).

We run test on current build distribution:

Running integration tests for Maven 4.0.0-alpha-8-SNAPSHOT
	using Maven executable: /home/jenkins/jenkins-home/workspace/Maven_maven-box_maven_MNG-7898/test/core-it-suite/target/apache-maven/bin/mvn
	with verifier.forkMode: auto

We only don't have populated local repo used by test by Maven build