Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11515 invoked from network); 5 Apr 2004 03:00:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Apr 2004 03:00:53 -0000 Received: (qmail 49360 invoked by uid 500); 5 Apr 2004 03:00:30 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 49307 invoked by uid 500); 5 Apr 2004 03:00:30 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 49291 invoked from network); 5 Apr 2004 03:00:30 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by daedalus.apache.org with SMTP; 5 Apr 2004 03:00:30 -0000 Received: (qmail 4262 invoked by uid 65534); 5 Apr 2004 03:00:38 -0000 Received: from A7188.a.pppool.de (EHLO gmx.de) (213.6.113.136) by mail.gmx.net (mp003) with SMTP; 05 Apr 2004 05:00:38 +0200 X-Authenticated: #3483660 Message-ID: <4070CC22.5050403@gmx.de> Date: Mon, 05 Apr 2004 05:01:54 +0200 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: de-de, de, en-us, en-gb, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: new blocks.properties way more painful to use References: <4070899F.4080706@apache.org> <4070C674.5040206@gmx.de> <37201.10.0.0.5.1081133612.squirrel@ags01.agsoftware.dnsalias.com> In-Reply-To: <37201.10.0.0.5.1081133612.squirrel@ags01.agsoftware.dnsalias.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 05.04.2004 04:53, Antonio Gallardo wrote: >>But the real need for changing it came out of the discussion about >>default excludes of blocks (e.g. javaflow or all unstable blocks). You >>have *no* possibility to re-include a block then in >>local.blocks.properties. > > > Yes you have a posibility. I posted, while I developed the OJB block I > found the way to do that: > > Suppose in block.properties you set: exclude.block.ojb=true > > Then to rewrite the value, you can use in your local.block.properties: > > exclude.block.ojb=false > > and this works. > > It is the "nature" of Ant properties. Once you set it, you cannot change > it. If I already set it in the local.block.properties, even in the case > you try to rewrite it in the block.properties you will not success and the > property remain as it was defined in the local.block.properties block. Ah, sorry, you are right. I found this out myself, but had it not in mind when writing the above: http://article.gmane.org/gmane.text.xml.cocoon.devel/33944 But exactly the "nature" of Ant properties or at least the behaviour when using them in @unless and @if (which is independent on their value true or false, only set or not set is tested) let me think that the above would not work. Only the mapping through made this work. And at the end the vote was even about just changing docu ("use true/false for default excluded blocks") or additionally rename the properties. Joerg