Hello, We have been discussing various ways to view what's happening internally with algorithms, and the topic of including SLF4J has come up. I know that this was discussed earlier and it was decided that CM is a low level dependency, therefore it should minimize the transitive dependencies that it introduces. The Java community has adopted many means of dealing with potential logging conflicts, so I'm requesting that we use SLF4J for logging.
I know that JBoss introduced its own logging system, and this made me a bit nervous about this suggestion, so I looked up strategies for switching their logger out with SLF4J: http://stackoverflow.com/questions/14733369/force-jboss-logging-to-use-of-slf4j The general process I go through when working with many dependencies that might use commons-logging instead of SLF4J looks something like this: http://stackoverflow.com/questions/8921382/maven-slf4j-version-conflict-when-using-two-different-dependencies-that-requi With JDK9 individual modules can define their own isolated set of dependencies. At this point the fix should be a permanent. If someone has has a very intricate scenario that we have not yet seen, they could use (And probably should use) OSGi to isolate dependencies. WDYT? Cheers, - Ole --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
