You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2010/09/10 00:47:33 UTC
[jira] Resolved: (WINK-295) Upgrade to SLF4J 1.6.0
[ https://issues.apache.org/jira/browse/WINK-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk resolved WINK-295.
-----------------------------
Assignee: Bryant Luk
Fix Version/s: 1.1.2
Resolution: Fixed
I made the change. Thanks for reporting, though now that I've made this change, (in tradition with us always being at least one version behind), I imagine SLF4J will release a new version next week. ;)
> 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.