I ask this because there seems to be several suggestions/enhancements that get shot down by the slf4j crew as 'too hard' etc...
Those argument/excuses simply don't fly in community projects because someone is always willing to do them. I'm not talking about changing the whole api, I completely agree with taking those types of changes slow and cautiously, however... My own bug/enhancement request (http://bugzilla.slf4j.org/show_bug.cgi?id=74) is to simply add the following to code to log4j bridge... Level getLevel() { return slf4jLogger.isTraceEnabled() ? Level.TRACE : slf4jLogger.isDebugEnabled() ? Level.DEBUG : slf4jLogger.isInfoEnabled() ? Level.INFO : slf4jLogger.isWarnEnabled() ? Level.WARN : Level.ERROR; } It was promptly closed with the excuse: "Given that Category class in log4j-over-slf4j is merely a wrapper around an SLF4J logger, and given that SLF4J loggers do not have a level, it is impossible to implement the getLevel() method. Moreover, as mentioned in the docs [1], log4j-over-slf4j is not a perfect log4j API replacement." 'Impossible'? It would take about 5 seconds to get that into the baseline and it would not harm the bridge at all. In fact it would make it a little more complete. So, I'd like to know if the slf4j project is a community effort or just an open source project. Either one is fine, it just clears up expectations (for me anyway). Thanks, Michael _______________________________________________ dev mailing list [email protected] http://www.slf4j.org/mailman/listinfo/dev
