commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRYPTO-75) ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT is not guaranteed constant
Date Sat, 25 Jun 2016 13:27:37 GMT

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

Sebb resolved CRYPTO-75.
------------------------
    Resolution: Fixed

Fixed in

CRYPTO-74 Full class names make code more difficult to update

CIPHER_CLASSES_DEFAULT is only used by CryptoCipherFactory so move it
there and make it private

Project: http://git-wip-us.apache.org/repos/asf/commons-crypto/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-crypto/commit/1a33867f
Tree: http://git-wip-us.apache.org/repos/asf/commons-crypto/tree/1a33867f
Diff: http://git-wip-us.apache.org/repos/asf/commons-crypto/diff/1a33867f



> ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT is not guaranteed constant
> ----------------------------------------------------------------------------------
>
>                 Key: CRYPTO-75
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-75
>             Project: Commons Crypto
>          Issue Type: Bug
>            Reporter: Sebb
>
> ConfigurationKeys#COMMONS_CRYPTO_CIPHER_CLASSES_DEFAULT contains a fully-qualified class
name.
> This is not guaranteed to be constant if the package names ever have to be changed.
> The constant should be changed to an alias that is handled by the runtime code when creating
the class.



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

Mime
View raw message