This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


    omit aa19eecafc Minor: Regenerated BOMs for 
7a22cc53996f48e454425970812f64fba8b5c907
     add c1c5db796a Bump org.apache.maven.plugins:maven-war-plugin from 3.5.0 
to 3.5.1 (#2341)
     add 70514120f5 Minor: Regenerated BOMs for 
c1c5db796ab732e1be0504f465bbc7aa7adc1eba

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   (aa19eecafc)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(70514120f5)

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/openejb-itests-web/pom.xml | 2 +-
 pom.xml                           | 2 +-
 tomee/tomee-plume-webapp/pom.xml  | 2 +-
 tomee/tomee-webapp/pom.xml        | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

Reply via email to