commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CONFIGURATION-604) combining properties which use 3+ part names discards entries as of Commons 1.6+
Date Mon, 13 Jul 2015 20:23:05 GMT

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

Oliver Heger resolved CONFIGURATION-604.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0

A fix was committed in revision 1690812. The problem was in the construction of a hierarical
configuration from a flat one; the algorithm could indeed produce different results based
on the order of the keys in the source configuration.

I did not look into the old sources for Configuration 1.5 to find out by which change the
problem was introduced. The fix should make the resulting hierarchical configuration more
independent on the order of property keys.

Many thanks for spotting this!

> combining properties which use 3+ part names discards entries as of Commons 1.6+
> --------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-604
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-604
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.6
>            Reporter: N Campbell
>             Fix For: 2.0
>
>
> When two property files are combined using commons config 1.5, the aggregate configuration
returns an expected result of 6 entries. If Commons configuration 1.6 or higher is used, the
resulting set drops to  which is not expected. 
> The property names include 2, 3 or 4 part names X.Y, X.Y.Z etc and it appears that as
of 1.6 if the names are arranged in 2 part, then 3 part etc that the combiner returns the
expected result.
> There does not appear to be any release notes etc that would suggest  that this isn't
a defect versus an intended implementation change.



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

Mime
View raw message