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 dedd4fa3a9 Minor: Regenerated BOMs for
09ded8c126bc3c6832bb3675f0ec79f1a41fb0e4
add 406289554f [tomee-10.x]: Bump
org.apache.maven.plugins:maven-compiler-plugin
new cd09eb0e22 Minor: Regenerated BOMs for
406289554f0918631fe84c0a8fe1f791f1916713
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 (dedd4fa3a9)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (cd09eb0e22)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 2 +-
tck/concurrency-standalone/pom.xml | 2 +-
tomee/apache-tomee/pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
