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
omit e0798c0ec6 Minor: Regenerated BOMs for
f4169222733dabacf4835f219e12f2394e8d3e9e
add 7a5a1f6419 [tomee-10.x]: Bump org.codehaus.mojo:templating-maven-plugin
add 59b78825eb Minor: Regenerated BOMs for
7a5a1f641925cfe62446730d783b9c956bc6746e
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 (e0798c0ec6)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (59b78825eb)
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:
itests/tomee-server-version/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
