This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
regenerate_boms_after_dep_upgrade_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard b1cda527da Minor: Regenerated BOMs for
710e5612c0b4b3d479fc4d0f09cd8963732efc70
add e84f2b221b [tomee-10.x]: Bump
org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom (#2536)
add 70dcc336ad Minor: Regenerated BOMs for
e84f2b221b596a563181a77114bad81088718745
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 (b1cda527da)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (70dcc336ad)
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:
arquillian/functional-tests/spring-cxf-tomee-4332/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
