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 1797552 Minor: Regenerated BOMs for
4c2066625e82203402c812b8964a3bbcf8e3a604
add 217870d Add some excludes to the TCK to make sure we use the same API
add 145d319 Move to Servlet 5 protocol
add 8dbe7b2 Minor: Regenerated BOMs for
145d319c0137680f2b18f205c250917616a99c0b
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 (1797552)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(8dbe7b2)
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:
tck/bval-tomee/pom.xml | 14 ++++++++++++++
tck/bval-tomee/src/test/resources/arquillian.xml | 1 +
2 files changed, 15 insertions(+)
