Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4AD0A6EF.4070501@oliver-heger.de>
Date: Sat, 10 Oct 2009 17:23:27 +0200
From: Oliver Heger <oliver.heger@oliver-heger.de>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [CONFIGURATION] Which CombinedConfiguration
References: <2bacf5dd0910071431o628d5309q69fd8d61143e64a6@mail.gmail.com>
 <4ACD7E9A.6010308@oliver-heger.de>
 <5AA6853D-EFDD-47D6-A99D-ACF6A5DEC6FD@dslextreme.com>
In-Reply-To: <5AA6853D-EFDD-47D6-A99D-ACF6A5DEC6FD@dslextreme.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ralph Goers schrieb:
> 
> On Oct 7, 2009, at 10:54 PM, Oliver Heger wrote:
> 
>> ralph.goers @dslextreme.com schrieb:
>>> I'm trying to port my changes to fix CONFIGURATION-390 from my trunk 
>>> sandbox
>>> to configuration2-experimental. But there are two CombinedConfiguration
>>> classes, one in the main directory and one under combined. Which one 
>>> should
>>> be removed and which needs the fix?
>>> Ralph
>> The one under combined should be the final one. Sorry for the confusion.
>>
> 
> This is a big problem for me. I tried switching 
> DefaultConfigurationBuilder to the combined/CombinedConfiguration and 
> got all kinds of errors in TestDefaultConfigurationBuilder (also 
> switching that to use combined). I've spent days trying to figure out 
> how to merge the CONFIGURATION-390 changes to the branch without much luck.
> 

Obviously the branch is a pretty mess with work started and not 
finished. I think DefaultConfigurationBuilder still uses the old classes 
because not all of its dependencies have been ported to use the 
AbstractHierarchicalConfiguration base class.

Meanwhile I work on some new ideas in the base package which are yet a 
different approach.

No idea how we can clean up things. Maybe I should do my new experiments 
in a new branch?

For the reloading problem I wonder whether it makes sense at all to 
apply these changes to the branch. IMHO we should redesign the reloading 
operations completely for configuration2.

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org