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 04ec0dc4d9 Minor: Regenerated BOMs for
f9055272034385d30938c9f0178512525d40526b
add 15e922358e [tomee-10.x]: Bump
org.apache.maven.plugins:maven-release-plugin (#2342)
add 2258971ae3 Minor: Regenerated BOMs for
15e922358ed19f6f4f8a9159380fc78a0375a870
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 (04ec0dc4d9)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (2258971ae3)
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(-)
