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

Posted to issues@commons.apache.org by "Dapeng Sun (JIRA)" <ji...@apache.org> on 2016/06/16 02:41:05 UTC

[jira] [Created] (CRYPTO-76) Remove log dependence

Dapeng Sun created CRYPTO-76:
--------------------------------

             Summary: Remove log dependence
                 Key: CRYPTO-76
                 URL: https://issues.apache.org/jira/browse/CRYPTO-76
             Project: Commons Crypto
          Issue Type: Bug
            Reporter: Dapeng Sun
            Assignee: Dapeng Sun


According the discussion in commons-dev, we will remove the log dependence of common-logging.
About the logging of native library failure, users of CRYPTO could get the information about whether native is enabled or native failure reason from org.apache.commons.crypto.utils.NativeCodeLoader#isNativeCodeLoaded() or org.apache.commons.crypto.cipher.Openssl#loadingFailureReason(), they could log these information in their system if they need.
At the same time, I think we can add an option for "native only" (Currently, when loading native failed, we log native failure error and use JCE implementation as fallback directly), the property in configuration may like "ENABLE_FALLBACK_ON_NATIVE_FAILED", if user disable the option, it could throw an exception when loading native failed.



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