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/08/12 18:20:46 UTC

(tomee) branch regenerate_boms_after_dep_upgrade updated (66a418cd03 -> 68d6fe3229)

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 66a418cd03 Minor: Regenerated BOMs for ed97d3b6495a045fc7db0aaad0addba236435b61
     add eac08a46a8 Bump ch.qos.logback:logback-classic from 1.1.7 to 1.5.6 in /examples
     add 68d6fe3229 Minor: Regenerated BOMs for eac08a46a88aa7806161b28ff0aecff8987ac1a6

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   (66a418cd03)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade (68d6fe3229)

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/tomee-jms-portability/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)