I was given the following log settings in the past from JB - this caused enough log noise to see what it happening in the background:
In etc/org.ops4j.pax.logging.cfg, you can enable trace on Pax URL and Aether: log4j2.logger.aether.name = shaded.org.eclipse.aether log4j2.logger.aether.level = TRACE log4j2.logger.http-headers.name = shaded.org.apache.http.headers log4j2.logger.http-headers.level = DEBUG log4j2.logger.maven.name = org.ops4j.pax.url.mvn log4j2.logger.maven.level = TRACE -----Original Message----- From: ntle <[email protected]> Sent: Thursday, 13 June 2019 1:25 PM To: [email protected] Subject: How to enable osgi bundle resolver tracing Hello, I;m using karaf 4.2.6, installing my feature (contains a few hundreds bundles) is fine but when i start my feature, karaf never finish. I suspect something wrong with the bundle resolution so i want to see how karaf resolve bundle dependencies. Is there a setting in org.ops4j.pax.logging.cfg for this? Thai Le -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
