Did you also reference the pax-jdbc feature in your feature file? You'll need to declare that dependency to be installed.
regards, Achim 2017-04-15 19:39 GMT+02:00 Steinar Bang <[email protected]>: > >>>>> You wrote: > > > For now, I will go back to the surefire config (it saves me the job of > > manually killing the leftover java processes, and gets further before > > it fails). > > Summary: The surefire "<forkCount>0</forkCount>" config didn't work, and > the leftover Java VM is a problem with surefire 2.19 and later > > With the surefire "<forkCount>0</forkCount>" config in place, the test > failed much earlier, before the karaf runtime was even ready to start: > [WARNING] useSystemClassloader setting has no effect when not forking > Running no.priv.bang.ukelonn.tests.UkelonnServiceIntegrationTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for > further details. > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.132 sec > <<< FAILURE! - in no.priv.bang.ukelonn.tests.UkelonnServiceIntegrationTest > no.priv.bang.ukelonn.tests.UkelonnServiceIntegrationTest Time elapsed: > 0.123 sec <<< ERROR! > java.lang.RuntimeException: Problem starting container > Caused by: java.net.MalformedURLException: unknown protocol: mvn > > no.priv.bang.ukelonn.tests.UkelonnServiceIntegrationTest Time elapsed: > 0.132 sec <<< ERROR! > java.lang.NullPointerException > at org.apache.maven.surefire.junit4.JUnit4Provider.execute( > JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > JUnit4Provider.java:161) > > The leftover Java VM is a surefire issue. It is an issue both with > surefire 2.19.1 that I was running, and the current surefire 2.20. > http://maven.40175.n5.nabble.com/surefire-forked-vm-failed- > tp5858900p5859320.html > > However, leftover VM isn't an issue with surefire 2.18, so I've > downgraded to surefire 2.18. > > Now I'm back to the issue of why the pax-jdbc feature isn't found: > 1. It's found in a regular karaf instance > 2. It didn't help specifying the feature repository containing the > feature pax-jdbc in my feature file > > All and any ideas are welcome! > > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
