This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-9327
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-junit-teleporter.git
discard 01a7811 SLING-9327 - Teleporter not working with jdk11 due to missing
xml bind classes
add 3de6bd0 SLING-11633 - Compile with Java 11 (#5)
add 1cb3357 SLING-9327 - Teleporter not working with jdk11 due to missing
xml bind classes
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 (01a7811)
\
N -- N -- N refs/heads/issue/SLING-9327 (1cb3357)
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(-)
