March 2017 - slf4j-dev - mailman3.qos.ch

[qos-ch/slf4j] a81440: fix date issue in news.html
by Ceki Gulcu 16 Mar '17

16 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: a81440ea36676f3b090f5a4ccba70d17c7b80f6e https://github.com/qos-ch/slf4j/commit/a81440ea36676f3b090f5a4ccba70d17c7b8… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- fix date issue in news.html

1 0

[qos-ch/slf4j]
by ceki 16 Mar '17

16 Mar '17

Branch: refs/tags/v_1.7.25 Home: https://github.com/qos-ch/slf4j

1 0

[qos-ch/slf4j] c2a7cc: prepare release 1.7.25
by Ceki Gulcu 16 Mar '17

16 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: c2a7cca6cbbba49e452522d2fa3358f83ccb2c99 https://github.com/qos-ch/slf4j/commit/c2a7cca6cbbba49e452522d2fa3358f83ccb… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-android/pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jcl/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml M slf4j-site/src/site/pages/news.html Log Message: ----------- prepare release 1.7.25

1 0

[qos-ch/slf4j] a84891: change serialVersionUID since internals changed
by Ceki Gulcu 16 Mar '17

16 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: a8489127b08bd5b8e1fa7ca5e5d33f93c0676986 https://github.com/qos-ch/slf4j/commit/a8489127b08bd5b8e1fa7ca5e5d33f93c067… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-16 (Thu, 16 Mar 2017) Changed paths: M slf4j-api/src/main/java/org/slf4j/helpers/BasicMarker.java Log Message: ----------- change serialVersionUID since internals changed

1 0

[qos-ch/slf4j] 60eb95: [license] Update copyright year to 2017
by Ceki Gulcu 10 Mar '17

10 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 60eb95e0f58728dea8e71f770cf5951ca8270ed2 https://github.com/qos-ch/slf4j/commit/60eb95e0f58728dea8e71f770cf5951ca827… Author: Jeremy Landis <jeremylandis(a)hotmail.com> Date: 2017-03-04 (Sat, 04 Mar 2017) Changed paths: M LICENSE.txt Log Message: ----------- [license] Update copyright year to 2017 Commit: 2fc2dc1deb3767b2c84a0d50eb5935f7fba59217 https://github.com/qos-ch/slf4j/commit/2fc2dc1deb3767b2c84a0d50eb5935f7fba5… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-10 (Fri, 10 Mar 2017) Changed paths: M LICENSE.txt Log Message: ----------- Merge pull request #173 from hazendaz/master [license] Update copyright year to 2017 Compare: https://github.com/qos-ch/slf4j/compare/2f06933ccd22...2fc2dc1deb37

1 0

[JIRA] (SLF4J-394) add renderThrowable() and renderLevel() protected methods + mark LOG_LEVEL_* protected in simple provider
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

[ https://jira.qos.ch/browse/SLF4J-394?page=com.atlassian.jira.plugin.system.… ] JIRA Administrator commented on SLF4J-394: ------------------------------------------ Hi Hervé, Thank you for reporting the "close" issue. Apparently, in order to close a JIRA issue, the reporter in addition to the "close" issue privilege has to have the "transition" issue privilege. The problem has been solved now. > add renderThrowable() and renderLevel() protected methods + mark LOG_LEVEL_* protected in simple provider > --------------------------------------------------------------------------------------------------------- > > Key: SLF4J-394 > URL: https://jira.qos.ch/browse/SLF4J-394 > Project: SLF4J > Issue Type: Improvement > Components: slf4j-simple > Affects Versions: 1.7.24 > Environment: Apache Maven 3.5 with maven-slf4j-provider http://maven.apache.org/ref/3-LATEST/maven-slf4j-provider/ > Reporter: Hervé Boutemy > Assignee: Ceki Gülcü > Fix For: 1.7.25 > > > Apache Maven created a Groovy monkey patch to extract such renderThrowable() and renderLevel() and being able to override these methods in a local provider, which is essentially slf4j-simple with a little rendering improvement > see [https://git-wip-us.apache.org/repos/asf/maven/?p=maven.git;a=blob;f=maven-s…] > Having these changes directly in slf4j simple provider should not change much things, and would avoid us the Groovy patch dependency: the provider will still be required, since we can't have 2 providers in the classpath, and adding real extension/configuration to slf4j simple is much more complex -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-399) test jira
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

[ https://jira.qos.ch/browse/SLF4J-399?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-399. ------------------------------ Resolution: Fixed Testing closing of JIRA issues. > test jira > --------- > > Key: SLF4J-399 > URL: https://jira.qos.ch/browse/SLF4J-399 > Project: SLF4J > Issue Type: Bug > Reporter: Dummy > Assignee: Ceki Gülcü > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-399) test jira
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

Dummy created SLF4J-399: --------------------------- Summary: test jira Key: SLF4J-399 URL: https://jira.qos.ch/browse/SLF4J-399 Project: SLF4J Issue Type: Bug Reporter: Dummy Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-398) Add a high service ranking to the registered LogService
by QOS.CH (JIRA) 09 Mar '17

09 Mar '17

Matt Magoffin created SLF4J-398: ----------------------------------- Summary: Add a high service ranking to the registered LogService Key: SLF4J-398 URL: https://jira.qos.ch/browse/SLF4J-398 Project: SLF4J Issue Type: Improvement Components: osgi-over-slf4j Affects Versions: 1.7.24 Environment: It would be nice of slf4j used a high service ranking when it registered {{LogService}} so it will take precedent over any built-in {{LogService}} provided by the OSGi runtime (e.g. Equinox). I figured if deploying the slf4j {{LogService}} most people would expect this implementation to be used, but that Equinox's built-in service is registered as well at the default service level so bundles importing {{LogService}} might get that one instead of the slf4j implementation. See https://github.com/qos-ch/slf4j/pull/174 Reporter: Matt Magoffin Assignee: SLF4J developers list Priority: Minor -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-396) Support jul sourceClassName and sourceMethodName in slf4j-bridge.
by QOS.CH (JIRA) 07 Mar '17

07 Mar '17

[ https://jira.qos.ch/browse/SLF4J-396?page=com.atlassian.jira.plugin.system.… ] Joern Huxhorn commented on SLF4J-396: ------------------------------------- A bit of extra context: I had my own bridge implementation in Lilith that was predating this one. Yours is the better implementation because it handles the resource bundles appropriately so I decided to drop my own implementation altogether in favor of the {{SLF4JBridgeHandler}}/{{LevelChangePropagator}} combination. The only downside is the lack of the info mentioned above which my implementation was previously already putting into the {{MDC}}. > Support jul sourceClassName and sourceMethodName in slf4j-bridge. > ----------------------------------------------------------------- > > Key: SLF4J-396 > URL: https://jira.qos.ch/browse/SLF4J-396 > Project: SLF4J > Issue Type: Improvement > Components: jul-to-slf4j > Affects Versions: 1.7.24 > Environment: any > Reporter: Joern Huxhorn > Assignee: SLF4J developers list > > The {{SLF4JBridgeHandler}} is currently dropping some log record info while bridging to slf4j. > The reason for this is that {{java.util.logging}} logger names are different beasts than slf4j ones. While it is a very common convention that an slf4j logger name equals the class name it's responsible for, this isn't necessarily the case for {{java.util.logging}}. > That's why {{LogRecord}} contains {{sourceClassName}} and {{sourceMethodName}} fields that are populated by {{Logger.entering}}, {{Logger.exiting}}, {{Logger.throwing}} and the general {{logp/logrb}} methods. > That info is crucial to the point where the log records are relatively useless without it. > Example: > {{Logger.entering("SourceClass","sourceMethod")}} will result in an event that simply says {{ENTRY}}. > Furthermore, {{jul}} allows for custom {{Level}} instances with a name and an arbitrary {{intValue()}}. While losing those is way less critical since they are already mapped to slf4j levels in a reasonable way, I think it would still be worthwhile to keep that info around. > I'd suggest to add the following to {{SLF4JBridgeHandler}}: > {code:java} > private static final String LEVEL_MDC_KEY = "JUL-Level"; > private static final String LEVEL_VALUE_MDC_KEY = "JUL-Level-Value"; > private static final String SOURCE_CLASS_NAME_MDC_KEY = "JUL-SourceClassName"; > private static final String SOURCE_METHOD_NAME_MDC_KEY = "JUL-SourceMethodName"; > private static void initMDC(LogRecord record) { > Level julLevel = record.getLevel(); > MDC.put(LEVEL_MDC_KEY, julLevel.getName()); > MDC.put(LEVEL_VALUE_MDC_KEY, Integer.toString(julLevel.intValue())); > String sourceClassName = record.getSourceClassName(); > if(sourceClassName != null) { > MDC.put(SOURCE_CLASS_NAME_MDC_KEY, sourceClassName); > } > String sourceMethodName = record.getSourceMethodName(); > if(sourceMethodName != null) { > MDC.put(SOURCE_METHOD_NAME_MDC_KEY, sourceMethodName); > } > } > private static void clearMDC() { > MDC.remove(LEVEL_MDC_KEY); > MDC.remove(LEVEL_VALUE_MDC_KEY); > MDC.remove(SOURCE_CLASS_NAME_MDC_KEY); > MDC.remove(SOURCE_METHOD_NAME_MDC_KEY); > } > {code} > Those methods would then be used in {{publish(LogRecord record)}}: > {code:java} > initMDC(record); > try { > if (slf4jLogger instanceof LocationAwareLogger) { > callLocationAwareLogger((LocationAwareLogger) slf4jLogger, record); > } else { > callPlainSLF4JLogger(slf4jLogger, record); > } > } > finally { > clearMDC(); > } > {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0