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 58ab788896 Minor: Regenerated BOMs for
b249664931a50d180a65466a47378e69af4ff93d
add 327a89cacf Bump org.codehaus.mojo:jaxb2-maven-plugin from 3.3.0 to
4.0.0
add 34f6a277e6 Minor: Regenerated BOMs for
327a89cacfe84ee9ecd678edbc3384fd985d0b13
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 (58ab788896)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(34f6a277e6)
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(-)
