You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by gi...@apache.org on 2024/11/18 08:51:04 UTC
(tomee) branch regenerate_boms_after_dep_upgrade updated (29d724ed39 -> f669a15950)
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 29d724ed39 Minor: Regenerated BOMs for 776c1d2e94e11d3896c548a611e0e83a94f23671
add a0085ca6e5 Bump org.apache.maven.plugin-tools:maven-plugin-annotations
add f669a15950 Minor: Regenerated BOMs for a0085ca6e53b70255db34ce21ed394297a0a791a
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 (29d724ed39)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade (f669a15950)
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:
maven/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)