You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2012/07/29 04:20:35 UTC
[jira] [Closed] (SHIRO-353) DefaultSecurityManager has invalid
SLF4J log instruction
[ https://issues.apache.org/jira/browse/SHIRO-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood closed SHIRO-353.
-------------------------------
Closing per the 1.2.1 release.
> DefaultSecurityManager has invalid SLF4J log instruction
> --------------------------------------------------------
>
> Key: SHIRO-353
> URL: https://issues.apache.org/jira/browse/SHIRO-353
> Project: Shiro
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Maciej Ziarko
> Priority: Trivial
> Fix For: 1.2.1, 1.3.0
>
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> Invalid SLF4J message (string concatenation with {} inside template) in DefaultSecurityManager class.
> Line 550:
> log.debug("Logging out subject with primary principal {}" + principals.getPrimaryPrincipal());
> Should be:
> log.debug("Logging out subject with primary principal {}", principals.getPrimaryPrincipal());
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira