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 258bc743cb Minor: Regenerated BOMs for
6375632b35ffcfb64c462060aa14e9a3e97750f3
add 2df9b3f3f3 Bump org.jboss.arquillian.junit5:arquillian-junit5-container
add 5cf6ee6745 Bump version.log4j2 from 2.6.2 to 2.23.1
add 81f7ebbdde Minor: Regenerated BOMs for
5cf6ee6745d16c134e0682487d266809c19a625e
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 (258bc743cb)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(81f7ebbdde)
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/junit5-arquillian-multiple-tomee/pom.xml | 2 +-
examples/junit5-arquillian-simple-websockets/pom.xml | 2 +-
examples/security-openid/pom.xml | 2 +-
maven/tomee-maven-plugin/pom.xml | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
