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 d7ce12e421 Minor: Regenerated BOMs for
29e5f9e92c85360c120e107d3f727c0c979bee12
add 2ef02b1239 TOMEE-4452 - commons-pool2 2.12.1
add 3dc3de6275 Minor: Regenerated BOMs for
2ef02b1239adb38325dc807df05ff9b27e25b20d
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 (d7ce12e421)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(3dc3de6275)
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:
boms/tomee-microprofile/pom.xml | 2 +-
boms/tomee-plume/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
boms/tomee-webprofile/pom.xml | 2 +-
pom.xml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
