This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard db719bcb17 Minor: Regenerated BOMs for
a6af27d0b87a7e524174d75612f41dfe91af7495
add abd93e07b3 TOMEE-4362 Commons IO 2.16.1
add 9bd5713ede Minor: Regenerated BOMs for
abd93e07b3e9994d4e73b4194f2617b46f98b173
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 (db719bcb17)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(9bd5713ede)
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:
examples/simple-webservice-without-interface/pom.xml | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
