This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12072
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-junit-core.git
omit d64b4fa SLING-12072 - Migrate sling.junit.core to jakarta.json
add 81ae642 SLING-12720 - Build fails on Java 21:Byte Buddy could not
instrument all classes within the mock's type hierarchy (#26)
new c400f48 SLING-12072 - Migrate sling.junit.core to jakarta.json
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 (d64b4fa)
\
N -- N -- N refs/heads/issue/SLING-12072 (c400f48)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 4 ++--
.../org/apache/sling/junit/annotations/AnnotationsTestSupport.java | 7 ++++++-
2 files changed, 8 insertions(+), 3 deletions(-)
