You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ra...@apache.org on 2026/09/17 10:46:34 UTC

(logging-log4j2) branch junit5-log4j-core-test updated (ac014aedd9 -> 679e8c0700)

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

ramanathan1504 pushed a change to branch junit5-log4j-core-test
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


 discard ac014aedd9 Migrate log4j-core-test to JUnit 5 and remove unused JUnit 4 rules
     add 788b5e6793 Migrate `log4j-core-test` to JUnit 5
     add 07c4e11295 Remove deprecated files
     add 880b96e513 Remove `junit-vintage` dependency
     add 679e8c0700 Complete `log4j-core-test` migration to JUnit 5 on current `2.x`

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   (ac014aedd9)
            \
             N -- N -- N   refs/heads/junit5-log4j-core-test (679e8c0700)

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: