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 2b7f7e2f55 Minor: Regenerated BOMs for
c57082d473c7f9c89461bb7136f9b8677a4e2fe5
add 7a22cc5399 Bump version.groovy from 5.0.2 to 5.0.3 (#2343)
add aa19eecafc Minor: Regenerated BOMs for
7a22cc53996f48e454425970812f64fba8b5c907
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 (2b7f7e2f55)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(aa19eecafc)
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:
tomee/tomee-webaccess/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
