This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a change to branch gh-mvn-3.9
in repository https://gitbox.apache.org/repos/asf/maven-integration-testing.git
discard a7e59d9e2 Use 3.9.4
discard 6928f4581 try with 4 alpha 7
discard f8a18ffb3 Use Maven 4.0.0-alpha-4 on GitHub
add 0b0bef68a [MNG-7895] Support ${project.basedir} in file profile
activation - fix ITs
add 5d1bf71f3 Add .java-version to .gitignore
add c6f314c7c Fix expectations on IT MNG-7836 following the modifications
on the consumer pom (#308)
add d59412eb6 [MNG-7895] Support ${project.basedir} in file profile
activation - fix ITs 3.9.5
add 4df756f0f Remove methods used for JUnit 3/4
add f0974ba23 Use Maven 4.0.0-alpha-4 on GitHub
add 07b963b3c try with 4 alpha 7
add 5b7426c49 Use 3.9.4
add 8d33f11ad Use 3.9.5 and wrapper with only-script
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a7e59d9e2)
\
N -- N -- N refs/heads/gh-mvn-3.9 (8d33f11ad)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/maven-verify.yml | 2 +-
.gitignore | 1 +
.../it/MavenITmng0947OptionalDependencyTest.java | 2 +-
.../it/MavenITmng2199ParentVersionRangeTest.java | 14 +-
...MavenITmng5608ProfileActivationWarningTest.java | 4 +-
.../it/MavenITmng7836AlternativePomSyntaxTest.java | 4 +-
.../maven/it/AbstractMavenIntegrationTestCase.java | 242 ++-------------------
7 files changed, 39 insertions(+), 230 deletions(-)
