You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Jiajia Li (JIRA)" <ji...@apache.org> on 2016/04/18 04:16:25 UTC

[jira] [Resolved] (DIRKRB-553) Unexpected import of slf4j to log4j12 bindings

     [ https://issues.apache.org/jira/browse/DIRKRB-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiajia Li resolved DIRKRB-553.
------------------------------
    Resolution: Fixed
      Assignee: Mauro Rocchi

Thanks for your contribution.

commit f77c4b3ed7329e0246494eef9a284f30cea2996e
Author: plusplusjiajia <ji...@intel.com>
Date:   Mon Apr 18 10:17:47 2016 +0800

    DIRKRB-553 Unexpected import of slf4j to log4j12 bindings. Contributed by Mauro Rocchi.

> Unexpected import of slf4j to log4j12 bindings
> ----------------------------------------------
>
>                 Key: DIRKRB-553
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-553
>             Project: Directory Kerberos
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC2
>            Reporter: Mauro Rocchi
>            Assignee: Mauro Rocchi
>
> Currently I'm testing an embedded KDC server into a standalone application and I've noted the {{slf4j-log4j12}} binding is imported in transitive way by the {{kerby-kdc-->kerby-config}} dependency.
> In my option the logging backend shouldn't be decided by a library, so I suggest to remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)