This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/org.junit-junit-bom-5.10.1
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git
omit 323d269 Bump org.junit:junit-bom from 5.9.0 to 5.10.1
add b849174 Replace XML configuration with JSON
add 5eb0d42 Fix version of modules removed from Log4j BOM
add 1f18d44 Fix dependency convergence
add 0dd6532 Fix versioning breaking the build
add 1c72117 Add Maven Central explictly to Dependabot config
add 38ebc1d Bump org.junit:junit-bom from 5.9.0 to 5.10.1
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 (323d269)
\
N -- N -- N
refs/heads/dependabot/maven/org.junit-junit-bom-5.10.1 (38ebc1d)
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/dependabot.yaml | 10 ++++++++
log4j-samples-jlink/src/main/resources/log4j2.json | 20 +++++++++++++++
log4j-samples-jlink/src/main/resources/log4j2.xml | 29 ----------------------
log4j-server/pom.xml | 3 +++
pom.xml | 22 ++++++++++++----
5 files changed, 50 insertions(+), 34 deletions(-)
create mode 100644 log4j-samples-jlink/src/main/resources/log4j2.json
delete mode 100644 log4j-samples-jlink/src/main/resources/log4j2.xml
