You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/07/05 12:43:10 UTC
[jira] [Resolved] (CRYPTO-105) Eliminate Configuration class
[ https://issues.apache.org/jira/browse/CRYPTO-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb resolved CRYPTO-105.
-------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
CRYPTO-105 Eliminate Configuration class
Project: http://git-wip-us.apache.org/repos/asf/commons-crypto/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-crypto/commit/8997a623
Tree: http://git-wip-us.apache.org/repos/asf/commons-crypto/tree/8997a623
Diff: http://git-wip-us.apache.org/repos/asf/commons-crypto/diff/8997a623
> Eliminate Configuration class
> -----------------------------
>
> Key: CRYPTO-105
> URL: https://issues.apache.org/jira/browse/CRYPTO-105
> Project: Commons Crypto
> Issue Type: Improvement
> Reporter: Sebb
> Fix For: 1.0.0
>
>
> As per discussion on the mailing list the Configuration class does not serve a particularly useful purpose.
> Several of the entries are internal use only, and the KEY entries belong more naturally in the classes that use the properties, e.g. the relevant factory classes.
> This also allows many of the KEY names to be shortened as they are now qualified by the class name where they are defined
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)