Hello
As guessed, it was tricky:
- custom Karaf distro had to be prepared to contain pax-logging bundles from current reactor
- logging configuration for pax-exam-container-karaf forked by maven-failsafe-plugin and forking another (3rd) JVM with Karaf itself has to be careful
Some findings/highlights:
- I created very slim pax-exam configuration for custom Karaf distro built just before the integration tests (separate Maven artifact)
- there are no conflicts between logging from Maven, logging from forked pax-exam and forked Karaf
- default service log provided by pax-logging-api (even before it starts! just after it resolves) works like a charm - bundle started BEFORE pax-logging-api can successfully log through SLF4J API
best regards
Grzegorz Grzybek