Hi, It will log the artifacts resolution (download). I would also add org.apache.karaf.feature logger to have some details about the resolver.
It will provide log messages similar to what we have with feature:install -t -v. Regards JB On 13/06/2019 05:50, [email protected] wrote: > 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 > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
