This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a change to branch ee11
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 168bd2d9d9 Move to Java 21 (as dictated by CXF)
discard 8b67caba5c Move to Java 21 (as dictated by CXF)
discard f53178c5c0 Move Version to 11
discard 0310b57dbc tomcat 11
add 98619e0f29 Minor: Regenerated BOMs for
794fbf2619007c59d8ed8a31472fb357cac192da
add 2f03467312 TOMEE-4538 - Tomcat 10.1.48
new ac1d4fd924 tomcat 11
new 3e3a9b9eba Move Version to 11
new eef22863db Move to Java 21 (as dictated by CXF)
new 2524be177e Move to Java 21 (as dictated by CXF)
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 (168bd2d9d9)
\
N -- N -- N refs/heads/ee11 (2524be177e)
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.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
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 +-
examples/datasource-versioning/pom.xml | 2 +-
examples/junit5-arquillian-simple-websockets/pom.xml | 2 +-
examples/websocket-tls-basic-auth/pom.xml | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
