Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 6 Jul 2016 05:51:11 +0000 (UTC)
From: "Dapeng Sun (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12986793.1467719582000.34041.1467784271065@Atlassian.JIRA>
In-Reply-To: <JIRA.12986793.1467719582000@Atlassian.JIRA>
References: <JIRA.12986793.1467719582000@Atlassian.JIRA> <JIRA.12986793.1467719582298@arcas>
Subject: [jira] [Updated] (CRYPTO-105) Eliminate Configuration class
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 06 Jul 2016 05:51:13 -0000


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

Dapeng Sun updated CRYPTO-105:
------------------------------
    Assignee: Sebb

> Eliminate Configuration class
> -----------------------------
>
>                 Key: CRYPTO-105
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-105
>             Project: Commons Crypto
>          Issue Type: Improvement
>            Reporter: Sebb
>            Assignee: 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)