<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Clojure Q&amp;A - Recent activity in tools.logging</title>
<link>https://ask.clojure.org/index.php/activity/contrib-libs/tools-logging</link>
<description></description>
<item>
<title>Commented: Using namespace as log originating class for JUL</title>
<link>https://ask.clojure.org/index.php/13427/using-namespace-as-log-originating-class-for-jul?show=13432#c13432</link>
<description>As stated the issue is when random lib users start getting these weird log statements into their std.err and they have very little to go on to start looking for the cause. Yes, obviously you can fix the format to elide that information.&lt;br /&gt;
&lt;br /&gt;
I understand that some take the position that this isn't the problem of c.t.l to solve, but I'd argue that the printout is caused by c.t.l macro and more importantly the issue is fixable mainly through a change to c.t.l.&lt;br /&gt;
&lt;br /&gt;
I advocate for this change because:&lt;br /&gt;
- there's no negative tradeoff&lt;br /&gt;
- the code complexity doesn't really increase&lt;br /&gt;
- improves performance (JUL doesn't need to perform reflection to figure out the caller class and method)&lt;br /&gt;
&lt;br /&gt;
I don't really see a downside to this change.</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/13427/using-namespace-as-log-originating-class-for-jul?show=13432#c13432</guid>
<pubDate>Mon, 06 Nov 2023 08:07:06 +0000</pubDate>
</item>
<item>
<title>Closed: Provide slf4j 2.0 factory for tools.logging?</title>
<link>https://ask.clojure.org/index.php/12390/provide-slf4j-2-0-factory-for-tools-logging?show=12390#q12390</link>
<description>&lt;p&gt;Is there interest in adding a slf4j 2 factory to clojure tools.logging ?&lt;/p&gt;
&lt;p&gt;slf4j 2 changed how it discovers implementations - now it uses java ServiceLoader (standard) facilities. &lt;/p&gt;
&lt;p&gt;On the client side version 1.x of API is compatible with version 2.x of API. &lt;br&gt;
Implementations however have changed - how the implementation is loaded.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.slf4j.org/faq.html#changesInVersion200&quot;&gt;https://www.slf4j.org/faq.html#changesInVersion200&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I don't think the old way of loading is working to find new slf4j 2.0 implementations that use service loader .&lt;br&gt;
&lt;a rel=&quot;nofollow&quot; href=&quot;https://github.com/clojure/tools.logging#selecting-a-logging-implementation&quot;&gt;https://github.com/clojure/tools.logging#selecting-a-logging-implementation&lt;/a&gt; (edited) .&lt;/p&gt;
&lt;p&gt;I could provide a PR if this is of interest. &lt;/p&gt;
</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/12390/provide-slf4j-2-0-factory-for-tools-logging?show=12390#q12390</guid>
<pubDate>Thu, 02 Feb 2023 15:46:34 +0000</pubDate>
</item>
<item>
<title>Answered: `condp = level#` in tools.logging</title>
<link>https://ask.clojure.org/index.php/10921/condp-level-in-tools-logging?show=10924#a10924</link>
<description>&lt;p&gt;Logged as &lt;a rel=&quot;nofollow&quot; href=&quot;https://clojure.atlassian.net/browse/TLOG-26&quot;&gt;https://clojure.atlassian.net/browse/TLOG-26&lt;/a&gt;&lt;/p&gt;
</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/10921/condp-level-in-tools-logging?show=10924#a10924</guid>
<pubDate>Mon, 09 Aug 2021 13:23:28 +0000</pubDate>
</item>
<item>
<title>Commented: Can I suppress low-level logs with tools.logging?</title>
<link>https://ask.clojure.org/index.php/8985/can-i-suppress-low-level-logs-with-tools-logging?show=9315#c9315</link>
<description>Just had this problem again, came back to this answer, and remembered how good it was. I wish I could give you another upvote. Thanks again!</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/8985/can-i-suppress-low-level-logs-with-tools-logging?show=9315#c9315</guid>
<pubDate>Wed, 20 May 2020 23:24:20 +0000</pubDate>
</item>
<item>
<title>Answered: Fix typo at README for `result is 1/2`</title>
<link>https://ask.clojure.org/index.php/8011/fix-typo-at-readme-for-result-is-1-2?show=8019#a8019</link>
<description>Reference: &lt;a href=&quot;https://clojure.atlassian.net/browse/TLOG-22&quot; rel=&quot;nofollow&quot; target=&quot;_blank&quot;&gt;https://clojure.atlassian.net/browse/TLOG-22&lt;/a&gt; (reported by pfeodrippe)</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/8011/fix-typo-at-readme-for-result-is-1-2?show=8019#a8019</guid>
<pubDate>Wed, 26 Jun 2019 12:00:00 +0000</pubDate>
</item>
<item>
<title>Answered: log/info removes quotes from strings making debugging harder than it needs to be.</title>
<link>https://ask.clojure.org/index.php/8010/info-removes-quotes-strings-making-debugging-harder-needs?show=8012#a8012</link>
<description>Reference: &lt;a href=&quot;https://clojure.atlassian.net/browse/TLOG-20&quot; rel=&quot;nofollow&quot; target=&quot;_blank&quot;&gt;https://clojure.atlassian.net/browse/TLOG-20&lt;/a&gt; (reported by llsouder)</description>
<category>tools.logging</category>
<guid isPermaLink="true">https://ask.clojure.org/index.php/8010/info-removes-quotes-strings-making-debugging-harder-needs?show=8012#a8012</guid>
<pubDate>Wed, 26 Jun 2019 12:00:00 +0000</pubDate>
</item>
</channel>
</rss>