April 2013 - slf4j-dev - mailman3.qos.ch

[Bug 190] New: juli-over-slf4j module
by bugzilla-daemon＠pixie.qos.ch 08 Jul '13

08 Jul '13

http://bugzilla.slf4j.org/show_bug.cgi?id=190 Summary: juli-over-slf4j module Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: olamy(a)apache.org Hi, Have a look at this fork : http://github.com/olamy/slf4j I have added a module to wrap juli logging library. Thanks -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 4

[Bug 239] New: performance issue in MessageFormatter
by bugzilla-daemon＠pixie.qos.ch 09 Jun '13

09 Jun '13

http://bugzilla.slf4j.org/show_bug.cgi?id=239 Summary: performance issue in MessageFormatter Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: kite668(a)mail.ru 1. org.slf4j.helpers.MessageFormatter.arrayFormat uses localy thread-safe StringBuffer instead of StringBuilder. I think it can be safely replaced. 2. "deeplyAppendParameter(sbuf, argArray[L], new HashMap());" - this is called for EVERY argument, even if it isn't array. I think instance of HashMap shouldn't be created for every argument. You can pass null and initialize HashMap in deeplyAppendParameter only for object's arrays and if it's previous value is null. Also you can initialize this map with initial capacity = array's size. 3. It will be very good if method arrayFormat would receive StringBuilder instead of creating instance of result String. This is common and more fast solution. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 3

[Bug 227] New: org.apache.log4j.Layout mistakenly in org.apache.log4j.spi
by bugzilla-daemon＠pixie.qos.ch 07 Jun '13

07 Jun '13

http://bugzilla.slf4j.org/show_bug.cgi?id=227 Summary: org.apache.log4j.Layout mistakenly in org.apache.log4j.spi Product: SLF4J Version: 1.6.x Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: jmsteward(a)gmail.com This may block development that should reference org.apache.log4j.Layout. Currently in the log4j-over-slf4j component Layout mistakenly exists at org.apache.log4j.spi and should be moved to org.apache.log4j. org.apache.log4j.Appender will need refactoring to remove the line "import org.apache.log4j.spi.Layout;". -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 4

[Bug 205] New: make multiple bindings check more intelligent
by bugzilla-daemon＠pixie.qos.ch 13 May '13

13 May '13

http://bugzilla.slf4j.org/show_bug.cgi?id=205 Summary: make multiple bindings check more intelligent Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Linux Status: NEW Severity: trivial Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: gsubes(a)gmail.com I'am using SLF4J in a setup of a software product line where multiple eclipse projects (as modules) are used with their own dependency management. so every module has its own copy of the logger binding jar. the modules have references to other modules (vie eclipse project references) and thus have multiple versions of the same logger binding in the classpath when tests are run etc. This results in always receiving this warning: SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-integration/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-integration-ws/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-webserver/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. -------------------------------- It would be nice if slf4j would check if the bindings actually have the same name and then ignore multiple jars of the same binding. the warning is made without a real reason in this particular case and should be more intelligent to allow such use cases. Or at least give me a hint on how to disable this warning on my own account. :) -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 4

[Bug 300] New: can't get the log output when run by maven tomcat plugin[mvn tomcat:run]
by bugzilla-daemon＠qos.ch 28 Apr '13

28 Apr '13

http://bugzilla.slf4j.org/show_bug.cgi?id=300 Priority: P5 Bug ID: 300 Assignee: slf4j-dev(a)qos.ch Summary: can't get the log output when run by maven tomcat plugin[mvn tomcat:run] Severity: enhancement Classification: Unclassified OS: Mac OS X 10.3 Reporter: stoneshao(a)gmail.com Hardware: PC Status: NEW Version: 1.6.x Component: Core API Product: SLF4J when I use mvn running tomcat ,with the following command: mvn tomcat:run I can access the web application after the embedded tomcat finishing start, but can't see any log info. and , I deploy the war file to a single tomcat ,start and run, the log can be displayed in console. I add slf4j-api,slf4j-log4j,log4j these dependencies with version 1.6.1. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[qos-ch/slf4j] c75ac9: refactor android logger
by Andrey Korzhevskiy 21 Apr '13

21 Apr '13

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: c75ac9a06d51da591a2217b32df347c11bfec40c https://github.com/qos-ch/slf4j/commit/c75ac9a06d51da591a2217b32df347c11bfe… Author: Andrey Korzhevskiy <a.korzhevskiy(a)gmail.com> Date: 2013-04-21 (Sun, 21 Apr 2013) Changed paths: M slf4j-android/src/main/java/org/slf4j/impl/AndroidLoggerAdapter.java M slf4j-android/src/main/java/org/slf4j/impl/AndroidLoggerFactory.java Log Message: ----------- refactor android logger

1 0

[qos-ch/slf4j] 06c4dd: upgrade to cal10 0.8.1, improved images
by Ceki Gulcu 18 Apr '13

18 Apr '13

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 06c4ddc080313a26a21a9cafa2475ccf0a6a36ba https://github.com/qos-ch/slf4j/commit/06c4ddc080313a26a21a9cafa2475ccf0a6a… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-04-18 (Thu, 18 Apr 2013) Changed paths: M pom.xml M slf4j-ext/src/test/java/org/slf4j/cal10n_dummy/Months.java A slf4j-ext/src/test/resources/production_en_UK.properties A slf4j-ext/src/test/resources/production_fr.properties M slf4j-site/src/site/images.src/concrete-bindings.odg M slf4j-site/src/site/images.src/legacy.odg M slf4j-site/src/site/resources/images/concrete-bindings.png M slf4j-site/src/site/resources/images/legacy.png Log Message: ----------- upgrade to cal10 0.8.1, improved images Commit: 47126546dc2e23aae466149616883320870f7b35 https://github.com/qos-ch/slf4j/commit/47126546dc2e23aae466149616883320870f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-04-18 (Thu, 18 Apr 2013) Changed paths: M slf4j-android/.gitignore R slf4j-android/default.properties A slf4j-android/project.properties M slf4j-android/src/main/java/org/slf4j/impl/AndroidLoggerFactory.java M slf4j-android/src/main/java/org/slf4j/impl/StaticLoggerBinder.java M slf4j-android/src/main/java/org/slf4j/impl/StaticMDCBinder.java M slf4j-android/src/main/java/org/slf4j/impl/StaticMarkerBinder.java Log Message: ----------- Merge branch 'master' of github.com:qos-ch/slf4j Compare: https://github.com/qos-ch/slf4j/compare/c268ca6aae05...47126546dc2e

1 0

[Bug 293] New: Unusable with Logback-ContextSelectors.
by bugzilla-daemon＠qos.ch 02 Apr '13

02 Apr '13

http://bugzilla.slf4j.org/show_bug.cgi?id=293 Summary: Unusable with Logback-ContextSelectors. Product: SLF4J Version: 1.7.x Platform: PC OS/Version: Windows XP Status: NEW Severity: blocker Priority: P1 Component: jcl-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: thomas.moeller(a)continentale.de Caching instances of Slf4j-Loggers prevents Logback-ContextSelectors from working. (See also bug 291 for a similar issue with the log4j bridge.) The caching code can be found in org.apache.commons.logging.impl.SLF4JLogFactory: public Log getInstance(String name) throws LogConfigurationException { Log instance = null; // protect against concurrent access of loggerMap synchronized (loggerMap) { instance = (Log) loggerMap.get(name); if (instance == null) { Logger logger = LoggerFactory.getLogger(name); if(logger instanceof LocationAwareLogger) { instance = new SLF4JLocationAwareLog((LocationAwareLogger) logger); } else { instance = new SLF4JLog(logger); } loggerMap.put(name, instance); } } return (instance); } -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3