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 bd42f318f4 Minor: Regenerated BOMs for
7ffe1d5af2256558650c39afe3f2225c5d3b81d7
add f5303b5586 [tomee-10.x]: Bump org.apache.felix:maven-bundle-plugin
(#2533)
add c15dc83b14 Minor: Regenerated BOMs for
f5303b55865877d678260ad6e46bc7f304c65e39
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 (bd42f318f4)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (c15dc83b14)
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:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
