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
omit 56eea52c72 Minor: Regenerated BOMs for
f8b169b671837fb5de537eb16220004044287b5e
add 548155f1ab [tomee-10.x]: Bump
org.apache.maven.plugins:maven-failsafe-plugin
add 5fdb42cd85 Minor: Regenerated BOMs for
548155f1ab0b8e070b2cbc37790beb99ae13332e
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 (56eea52c72)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (5fdb42cd85)
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 +-
1 file changed, 1 insertion(+), 1 deletion(-)
