Could my situation, where the feature loads without problems in a karaf instance but fails in the pax exam test, be caused by pax exam forking the JVM to start karaf?
The database is in memory after all, so the problem could be that the database disappears in mid test? (But if this is the case, why does the test work with liquibase 4.23.0 but fail with 4.23.1 or later?) So am I barking up the wrong tree? Or could the problem have something to do with the version of Aries SPI Fly used? Thanks!
