Chris Holmes ha scritto: > Ok, I'm trying to get a handle on this issue. > > One question, what's the objection to just using SFL4J ? > > It seems to meet Justin's criteria of using a standard library, it'll > work with sfl4j/jetty ;) (for Andrea), and Martin likes it a lot better > than commons logging. > > I imagine I just missed what the objection was, but I'm curious to hear it.
sfl4j is just a facade like commons logging. Now, in Jetty by default they put an implementation of the library that redirects to "simple logging". Given that it's the first element in the classpath it'll override whatever implementation we put in our library, meaning that we would not be able to force log4j usage unless we manually change the jars in the Jetty container (remember, slf4j way of doing redirections is to implement exactly the same classes in the different jars and have classloading decide which one gets used). I guess the second problem is timing, the slf4j is different enough from java logging (http://www.slf4j.org/api/org/slf4j/Logger.html) that manual changes will have to be performed manually instead of using a single search and replace, especially in the modules managed by Martin. Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
