This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.eclipse.aether-aether-api-1.1.0
in repository https://gitbox.apache.org/repos/asf/maven-reporting-impl.git
discard a7b2715 Bump org.eclipse.aether:aether-api from 1.0.0.v20140518 to
1.1.0
add 8464ab9 Bump org.junit:junit-bom from 5.10.1 to 5.10.2
add 34de836 [MSHARED-1361] Upgrade plugins and components (in ITs) (2)
add cefa8b0 [maven-release-plugin] prepare release
maven-reporting-impl-4.0.0-M14
add 4dae8a7 [maven-release-plugin] prepare for next development iteration
add 6b43e29 Bump org.eclipse.aether:aether-api from 1.0.0.v20140518 to
1.1.0
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 (a7b2715)
\
N -- N -- N
refs/heads/dependabot/maven/org.eclipse.aether-aether-api-1.1.0 (6b43e29)
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:
pom.xml | 14 +++++++-------
src/it/setup-reporting-plugin/pom.xml | 3 +++
src/it/use-as-direct-mojo-2/verify.groovy | 7 ++-----
src/it/use-as-direct-mojo/verify.groovy | 7 ++-----
4 files changed, 14 insertions(+), 17 deletions(-)
