You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/09/10 02:52:33 UTC
[jira] Commented: (WINK-295) Upgrade to SLF4J 1.6.0
[ https://issues.apache.org/jira/browse/WINK-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907848#action_12907848 ]
Hudson commented on WINK-295:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #382 (See [https://hudson.apache.org/hudson/job/Wink-Trunk-JDK1.5/382/])
Upgrade to SLF4J 1.6.1
Thanks to Jason Dillon for reporting the issue.
See [WINK-295]
> Upgrade to SLF4J 1.6.0
> ----------------------
>
> Key: WINK-295
> URL: https://issues.apache.org/jira/browse/WINK-295
> Project: Wink
> Issue Type: Improvement
> Components: Common
> Affects Versions: 1.1.2
> Reporter: Jason Dillon
> Assignee: Bryant Luk
> Fix For: 1.1.2
>
>
> {quote}
> As of SLF4J version 1.6.0, in the absence of an SLF4J binding, slf4j-api will default to a no-operation implementation discarding all log requests. Thus, instead of throwing an exception, SLF4J will emit a single warning message about the absence of a binding and proceed to discard all log requests without further protest. See also the relevant sectionin the user manual.
> {quote}
> ( from http://slf4j.org/news.html )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.