This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
regenerate_boms_after_dep_upgrade_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 28c8c43c38 Minor: Regenerated BOMs for
590a03b25199638d15c9cec2124876d1fc2ac884
add 39ffe87adc [tomee-10.x]: Bump
org.apache.maven.plugins:maven-resources-plugin
add 1c9b8add2a [tomee-10.x]: Bump org.projectlombok:lombok from 1.18.42 to
1.18.44
add 719058a01a Minor: Regenerated BOMs for
1c9b8add2a0f25c75cb1f3c9e386dd8fac0975d4
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 (28c8c43c38)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (719058a01a)
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 | 2 +-
tomee/apache-tomee/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
