sufyanharoon commented on PR #7:
URL: 
https://github.com/apache/sling-org-apache-sling-junit-teleporter/pull/7#issuecomment-2055066934

   @rombert, yes adding the two additional jars to the class path should fix 
this issue but before we upgraded to Java 11, it used to work seamlessly. This 
is a side effect of update of Java 11 where we have updated certain 
dependencies.
   As I stated earlier, anyone using latest teleporter will have to add these 
dependencies in their test class path. For that, the same should be documented 
on teleporter's 
[page](https://sling.apache.org/documentation/bundles/org-apache-sling-junit-bundles.html)
 under upgrade to Java 11 runtime otherwise everyone will struggle with the 
same issue that faced. 
   
   Do you see any issues in adding these additional jars as dependencies? These 
will make update to Java 11 and general usage of teleporter seamless. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to