> Possible solution/workaround > ---------------------------- > Now, I saw someone suggest this problem is avoidable, ie by putting in > place an alternative implementation for commons-logging which intercepts > stuff like getInstance(), perhaps always providing a NoOpLog. This > sounds like a workable, easily implementable idea, even if it feels > 'hacky'. IIUC what would happen is we put in place > > commons-logging-noop.jar (commons-stub.jar) > commons-cli.jar > commons-lang.jar > commons-(...).jar > > and never again get anxious about > > <dependency><id>commons-logging</id></dependency>
FYI, commons-lang and commons-collections do not depened on [logging], nor are they likely to do so. ([lang]s charter pretty much excludes it for example) Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
