On Sunday, December 22, 2019 5:34:02 AM CET Jean-Baptiste Onofré wrote: > Hi Achim,
Hi, > Serge reported the same on Unomi. > > I gonna check as, on Jenkins, Karaf itests (based on Pax Exam 4.13.1) > are working fine. > > The think I did for JDK9+ is: > > https://github.com/apache/karaf/blob/master/itests/common/src/main/java/org/ > apache/karaf/itests/KarafTestSupport.java#L184 > > So, if your tests extend KarafTestSupport, it should be straight forward. > If you don't extend KarafTestsSupport, you have to mimic the configuration. We have done it similar for Sling: https://github.com/apache/sling-org-apache-sling-karaf-integration-tests/blob/ master/src/main/java/org/apache/sling/karaf/testing/KarafTestSupport.java#L151 And it reminds me to open a PR because the duplication of options in Karaf's KarafTestSupport is really ugly. Regards, O. > Regards > JB > > On 21/12/2019 17:39, Achim Nierbeck wrote: > > Hi, > > > > it's one of those days where it's better to just stop for now. > > Though I've spent quite some time on figuring out, without real success > > though. > > Maybe one on the list does have a bright moment to point me into the > > right direction :) > > I was working on upgrading the latest dependencies for my karaf+vertx > > project. [1] > > And while on it I was trying to build with Java 11. Now what really > > puzzled me, the Pax-Exam tests all failed because the test container > > never really started. When trying to start the container alone, > > everything runs smoothly. Therefore it's something I'm missing with the > > pax-exam setup. > > I'd be grateful for any input on where I'm wrong :) > > > > Thanks, Achim > > > > > > [1] - https://github.com/ANierbeck/Karaf-Vertx/tree/jdk11
