Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E68CEE6.1070900@anyware-tech.com>
Date: Fri, 07 Mar 2003 17:55:02 +0100
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3b) Gecko/20030210
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: The new build system
References: <3E553E42.2030106@apache.org> <83smucox8a.fsf@bog.fiz-chemie.de>
 <3E5CA081.6040206@apache.org> <83fzqbp8g4.fsf@bog.fiz-chemie.de>
 <3E68CA7C.8040208@anyware-tech.com> <3E68CC47.9080508@apache.org>
In-Reply-To: <3E68CC47.9080508@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Stefano Mazzocchi wrote:

> Sylvain Wallez wrote:
>
>> Failed on the same problem today. For those targets that we want to 
>> exclude in the default build, having a "exclude.xxx=true" in 
>> build.properties requires to modify this CVS-managed file to allow 
>> building "xxx", which obviously isn't good.
>
>
> the exclude.* stuff that is not commented out in the build.properties 
> will be in the future so the problem goes away.


Do you mean that "in the future", the default will be for the build 
system to exclude nothing ?

Can't "the future" be right now and then let the user choose what he 
wants to exclude using its local.build.properties instead of patching 
build.properties ?

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }