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
omit 8092356a21 Minor: Regenerated BOMs for
438eb8ca3b36731e97541b4f3efd9bbf1284e22a
omit 438eb8ca3b Bump
org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven
omit 8e913baed6 Bump com.github.dasniko:testcontainers-keycloak from 3.3.1
to 3.4.0
omit 7be12ec731 Bump org.ow2.asm:asm from 9.2 to 9.7
add 98237b10cd Minor: Regenerated BOMs for
ade4be7a95a14297606463f859c0aabd0a66eee4
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 (8092356a21)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(98237b10cd)
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/async-servlet/pom.xml | 2 +-
examples/security-openid/pom.xml | 2 +-
examples/simple-jms-context/pom.xml | 2 +-
examples/simple-jms/pom.xml | 2 +-
examples/websocket-jms/pom.xml | 2 +-
mp-jwt/pom.xml | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
