Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: List of issues with samples (RE: Samples not working!!!!!!) 
Date: Fri, 18 Jan 2002 14:20:17 +0100
Message-ID: <GMEBIBHGAOFGJCDPJANDIEJJDHAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <007401c1a020$6ca90b60$6150000a@flagship.ru>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="iso-8859-1"

Piroumian, Konstantin wrote:

>
>
> IMO, it's not a very good idea to determine which parts of Cocoon
> one need,
> depending on presence of *.jars. So, for example, if in case when I don't
> need some optional component then I have to delete its JAR from my Cocoon
> repository and run build after that. Next time I'll have to copy
> it back to
> try it.
>
> It'll be much better to have a special build option for optional parts.
> Maybe a list of needed extensions in a .property file. E.g.:
>
> build webapp -Dinclude-ext=mini-cocoon.properties
> build webapp -Dinclude-ext=cocoon-with-deli.properties
> etc.
>

Yes, you're absolutely right and - believe it or not - I tried to put
something like
you suggested into the build system several weeks ago. As you can imagine
without success. The main problem for me was to combine the two conditions:
the availability of the tested optional class and the definition of the
build option. For this something like an "and" condition is required, which
I didn't find in ant - so I gave up...

Carsten


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