This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugin-tools-maven-plugin-annotations-3.13.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-tools.git
omit 41ab6f7 Bump org.apache.maven.plugin-tools:maven-plugin-annotations
add bc33fa0 Update `org.codehaus.modello:modello-maven-plugin` to version
`2.4.0` (#119)
add f8b0cb4 Fix handling of subclassed plugins in Log4j Docgen (#117)
add f9e80c3 Revert "Fix handling of subclassed plugins in Log4j Docgen
(#117)"
add 76d54b1 Bump org.apache.maven.plugin-tools:maven-plugin-annotations
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 (41ab6f7)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugin-tools-maven-plugin-annotations-3.13.0
(76d54b1)
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:
log4j-tools-parent/pom.xml | 2 +-
.../update_org_codehaus_modello_modello_maven_plugin.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
copy src/changelog/{0.8.0 =>
.0.x.x}/update_org_codehaus_modello_modello_maven_plugin.xml (72%)
