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
discard 1256c7ff2d Minor: Regenerated BOMs for
2eddcff5af5d56492b6dc40dfe6f2f9a443d1c24
omit 2eddcff5af Bump com.microsoft.azure:azure-webapp-maven-plugin in
/examples
add 8dbce4cc5b Minor: Regenerated BOMs for
089a9b4e064ec48c56772aa69d34e970c1e94bef
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 (1256c7ff2d)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(8dbce4cc5b)
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:
examples/cloud-tomee-azure/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
