This is an automated email from the ASF dual-hosted git repository.
olamy pushed a change to branch jenkinsfile-mimir
in repository https://gitbox.apache.org/repos/asf/maven.git
discard fa0e037a45 copy to .mvn/extensions.xml
discard 3c4fef4e80 copy to ~/.m2/extensions.xml
discard 0ff3324a35 build with 4.0.0-rc3, mimir extension in user home
discard 10c13b6884 test mimir with Jenkinsfile
add d47dfb68c4 [MNG-8679] Align superpom with mvn3 (#2246)
add 9a4c067943 Bump org.codehaus.plexus:plexus-interpolation from 1.27 to
1.28
add 6abf74d9ce Bump mockitoVersion from 5.16.1 to 5.17.0
add 1f5cb78071 Bump
io.github.olamy.maven.plugins:jacoco-aggregator-maven-plugin
add a6e1b51e6d Bump org.codehaus.plexus:plexus-xml from 4.0.4 to 4.1.0
add 1089f7518e test mimir with Jenkinsfile
add f8fdcfcad8 build with 4.0.0-rc3, mimir extension in user home
add fa281028ee copy to ~/.m2/extensions.xml
add fbc63f3399 copy to .mvn/extensions.xml
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 (fa0e037a45)
\
N -- N -- N refs/heads/jenkinsfile-mimir (fbc63f3399)
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:
.../resources/org/apache/maven/model/pom-4.0.0.xml | 8 --------
.../resources/org/apache/maven/model/pom-4.0.0.xml | 8 --------
.../maven/it/MavenITmng3843PomInheritanceTest.java | 18 +++---------------
pom.xml | 8 ++++----
4 files changed, 7 insertions(+), 35 deletions(-)
