Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44FD894A.7060909@mobilebox.pl>
Date: Tue, 05 Sep 2006 16:27:22 +0200
From: Leszek Gawron <lgawron@mobilebox.pl>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Properties - on and on
References: <44FD602F.2020709@mobilebox.pl> <44FD87C7.3000708@apache.org>
In-Reply-To: <44FD87C7.3000708@apache.org>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:
> Leszek Gawron wrote:
>> Why are most properties residing in 
>> cocoon-webapp/src/main/webapp/WEB-INF/cocoon/properties instead of 
>> cocoon-core/src/main/resources/META-INF/properties? This way if anybody 
>> changes anything also both archetypes have to be updated.
>>
>> After all we have property overrides and they do not even have to be 
>> generated by cocoon webapp archetype. The default properties should come 
>> from cocoon-core with the possibility to override in a particular cocoon 
>> mode.
>>
> Yes, I agree - each block and this includes core should have their own
> properties defined in resources/META-INF/properties to give default
> values. So in the end, Cocoon can run without any additional property
> file from the user.
Ok. I am going to follow what you said and migrate all possible 
properties to core.


-- 
Leszek Gawron, IT Manager                          MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65