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 683842b Minor: Regenerated BOMs for
0125401b011824b87921cfb92ba71b57cbd7f767
add 331e4a4 Minor: Disable generation of dependency-reduced-pom.xml files
for activemq shades
add d6ede68 Merge remote-tracking branch 'origin/master'
add ea44e85 Minor: Adjusts JUnit5 Simple Websockets with Arquillian for
EE9
add e2d01af Minor: Adjusts JUnit5 Multiple TomEE with Arquillian for EE9
usage
add ddc4eed Minor: Adjusts JUnit5 ApplicationComposer for EE9 usage
add d044829 Minor: Regenerated BOMs for
ddc4eed1af619162b4c22cce21cebf4d8cc3edba
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 (683842b)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(d044829)
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:
deps/activemq-broker-shade/pom.xml | 2 +-
deps/activemq-client-shade/pom.xml | 2 +-
deps/activemq-ra-shade/pom.xml | 2 +-
examples/junit5-application-composer/pom.xml | 24 ++++----------------
examples/junit5-arquillian-multiple-tomee/pom.xml | 24 ++++----------------
.../README.adoc | 2 +-
.../junit5-arquillian-simple-websockets/pom.xml | 26 +++++-----------------
.../src/main/resources/META-INF/beans.xml | 5 +++--
.../src/main/webapp/WEB-INF/web.xml | 5 +++--
9 files changed, 23 insertions(+), 69 deletions(-)
