John Casey schrieb: > This would be because of the recent addition of log4j, which is now > shaded into the Maven binary (bundled with a changed package structure > to keep it out of the way of plugins' own log4j dependencies). > httpclient is using log4j because it's available, but log4j doesn't have > a configuration included...resulting in this error.
If the core depends on something using commons-logging, then the core should also configure commons-logging, IMHO. Maybe the core better provides a commons-logging configuration disabling any use of the thread context classloader ? /** * The name (<code>use_tccl</code>) of the key in the config file used * to specify whether logging classes should be loaded via the thread * context class loader (TCCL), or not. By default, the TCCL is used. */ public static final String TCCL_KEY = "use_tccl"; Regarding the vote: 0 (non binding) -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
