You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/15 21:51:39 UTC

[jira] [Resolved] (CONFIGURATION-475) Deprecate ConfigurationKey class

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

Oliver Heger resolved CONFIGURATION-475.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.8

Fixed in revision 1231749.
                
> Deprecate ConfigurationKey class
> --------------------------------
>
>                 Key: CONFIGURATION-475
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-475
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.7
>            Reporter: Oliver Heger
>            Assignee: Oliver Heger
>            Priority: Minor
>             Fix For: 1.8
>
>
> The classes {{ConfigurationKey}} and {{DefaultConfigurationKey}} (from the _tree_ package) are almost identical. The major difference is that {{DefaultConfigurationKey}} is associated with a {{DefaultExpressionEngine}} instance and thus can produce correct keys even if the separator characters have been changed. There is little point in keeping both, so {{ConfigurationKey}} should be deprecated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira