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] [Commented] (CONFIGURATION-604) combining properties which use 3+ part names discards entries as of Commons 1.6+
Date Sat, 04 Jul 2015 20:04:04 GMT

    [ https://issues.apache.org/jira/browse/CONFIGURATION-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614033#comment-14614033
] 

Oliver Heger commented on CONFIGURATION-604:
--------------------------------------------

This seems to be a pretty old change since version 1.6 was released years ago.

To make sure I fully understand the problem, could you please specify exactly the expected
result and the actual result? (Or even better: could you transform your demo code fragment
to a unit test?)

> 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
>
> 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