>>>>> Achim Nierbeck <[email protected]>: > the karaf container is always a forked process. If you want to run it as > non-forked you can use the following configuration:
> runEmbedded(true) > this is especially useful if you want to debug your tests, but beware > because of the nature of how the tests run, this can only be used with > debugging and one test-method. Right. In the meantime I've found this thread http://karaf.922171.n3.nabble.com/Pax-exam-tests-fail-to-start-properly-with-Karaf-4-0-4-tp4044841p4044843.html and have applied the same cure: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <forkCount>0</forkCount> </configuration> </plugin> And that works... that is: it still doesn't start, but at least there isn't a Java VM still running after the test has failed. Does this the trigger the same behaviour as the runEmbedded(true) configuration? Or is that a competely different mechanism?
