Martin Desruisseaux ha scritto: > Andrea Aime a écrit : >> I understand the problem, but I have the feeling the extra code >> complexity added by that code is worse than then problem it tries >> to deal with. > > Okay. Then lets make CommonsLogger and Log4JLogger public and deprecate > LoggingFramework (please commit if you wish). I will delete LoggingFramework a > little bit later and investigate a bit which exception we could make explicit > (maybe catching ClassDefNotFoundError in some place and retrown them as the > checked ClassNotFoundException in setLoggerFactory method, if we can).
Will do.. just wondering, since LoggingFramework is @since 2.4 doesn't it make sense to just remove it? I mean, it has been around for just one day? I'll manage the commits and the tests (I'm also trying out the gt remove prefix branch in the meantime). 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
