sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (Jira)" <>
Subject [jira] [Commented] (SLING-9327) Teleporter not working with jdk11 due to missing xml bind classes
Date Wed, 08 Apr 2020 10:05:00 GMT


Bertrand Delacretaz commented on SLING-9327:

bq. now that Thierry Ygé confirmed that the only problem with version 1.0.18+ is the missing
osgi.core dependency?

I'm not 100% sure if that's what Thierry means.

[~petitbear68] could you confirm that reverting to using {{java.util.Base64}} would work for
you? As opposed to using {{commons-codec}} which I switched to in the commit that Konrad wants
us to revert (which I agree is a good idea in principle).

> Teleporter not working with jdk11 due to missing xml bind classes
> -----------------------------------------------------------------
>                 Key: SLING-9327
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.10
>            Reporter: Thierry Ygé
>            Priority: Blocker
>             Fix For: JUnit Tests Teleporter 1.0.22
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
> Currently when using teleporter on jdk11 based environment, the teleporter is failing
due to missing class.
> {quote}java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at
at com.adobe.granite.testing.serverside.rules.GraniteSSTRule$1.evaluate(
> {quote}
> This is due to jdk not containing this package anymore since jdk 9.
> Teleporter used is 1.0.10 and with 1.0.20 I couldn't use it as it fails with missing
osgi core dependency, unless I would then add it manually in the test module pom.
> Note from [~bdelacretaz]
> As per [] it
looks like using {{jakarta.xml.bind}} as an additional dependency might fix this.

This message was sent by Atlassian Jira

View raw message