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 f49a709b97 Minor: Regenerated BOMs for
69219eb009339d9b123ee2bdf4f0a1d8300df6d1
add cbe6f870e8 [tomee-10.x]: Bump org.codehaus.gmavenplus:gmavenplus-plugin
add 9e07e0b3c9 Minor: Regenerated BOMs for
cbe6f870e8719c8c96ed0cf47f0ae659986a0739
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 (f49a709b97)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (9e07e0b3c9)
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(-)
