You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/08/03 11:32:00 UTC

[jira] [Commented] (SLING-9327) Teleporter not working with jdk11 due to missing xml bind classes

    [ https://issues.apache.org/jira/browse/SLING-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169942#comment-17169942 ] 

Bertrand Delacretaz commented on SLING-9327:
--------------------------------------------

[~kwin] sorry I missed this earlier, I was away most of July and only got to this now.

I see that version 1.0.22 has been released with the modified code that requires {{commons-codec}}. Do you still think we should revert? I'd rather keep the current code considering it's been released. The additional dependency is not an "exotic" one, we're using commons-code in other places already.

> Teleporter not working with jdk11 due to missing xml bind classes
> -----------------------------------------------------------------
>
>                 Key: SLING-9327
>                 URL: https://issues.apache.org/jira/browse/SLING-9327
>             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.24
>
>          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 org.apache.sling.testing.teleporter.client.TeleporterHttpClient.setConnectionCredentials(TeleporterHttpClient.java:63) at org.apache.sling.testing.teleporter.client.TeleporterHttpClient.getHttpGetStatus(TeleporterHttpClient.java:136) at org.apache.sling.testing.teleporter.client.TeleporterHttpClient.waitForStatus(TeleporterHttpClient.java:75) at org.apache.sling.testing.teleporter.client.TeleporterHttpClient.installBundle(TeleporterHttpClient.java:94) at org.apache.sling.testing.teleporter.client.ClientSideTeleporter.installTestBundle(ClientSideTeleporter.java:173) at org.apache.sling.testing.teleporter.client.ClientSideTeleporter.access$000(ClientSideTeleporter.java:45) at org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:207) at com.adobe.granite.testing.serverside.rules.GraniteSSTRule$1.evaluate(GraniteSSTRule.java:104)
> {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 [https://stackoverflow.com/questions/52502189/java-11-package-javax-xml-bind-does-not-exist] it looks like using {{jakarta.xml.bind}} as an additional dependency might fix this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)