Return-Path: 
 <forrest-dev-return-7605-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org
Received: (qmail 98704 invoked from network); 1 Oct 2003 10:30:18 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 1 Oct 2003 10:30:18 -0000
Received: (qmail 20809 invoked by uid 500); 1 Oct 2003 10:30:01 -0000
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 20675 invoked by uid 500); 1 Oct 2003 10:30:00 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 20650 invoked from network); 1 Oct 2003 10:29:59 -0000
Received: from unknown (HELO mail.messagingengine.com) (66.111.4.25)
  by daedalus.apache.org with SMTP; 1 Oct 2003 10:29:59 -0000
Received: from mail.messagingengine.com (localhost [127.0.0.1])
	by localhost.localdomain (Postfix) with ESMTP id 581AB24DF48
	for <forrest-dev@xml.apache.org>; Wed,  1 Oct 2003 06:30:13 -0400 (EDT)
Received: from 10.202.2.150 ([10.202.2.150] helo=mail.messagingengine.com) by
 messagingengine.com
  with SMTP; Wed, 01 Oct 2003 06:30:13 -0400
X-Epoch: 1065004213
X-Sasl-enc: ND2OxTlwIveEVR16Qu3pdg
Received: from upaya.co.uk (unknown [213.48.13.34])
	by www.fastmail.fm (Postfix) with ESMTP id CB1D124DFE9
	for <forrest-dev@xml.apache.org>; Wed,  1 Oct 2003 06:30:12 -0400 (EDT)
Message-ID: <3F7AAC89.7040606@upaya.co.uk>
Date: Wed, 01 Oct 2003 11:29:29 +0100
From: Upayavira <uv@upaya.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: [RT] CLI and Forrestbot (was Re: New Forrestbot in the works (Re:
 forrestbot configuration))
References: <Pine.LNX.4.58.0309301446200.13397@delorean.solidusdesign.com>
 <20030930224446.GA31518@minotaur.apache.org>
In-Reply-To: <20030930224446.GA31518@minotaur.apache.org>
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

Jeff Turner wrote:

>On Tue, Sep 30, 2003 at 02:52:30PM -0400, Dave Brondsema wrote:
>  
>
>>I'm trying to set configuration files for forrestbot to generate several
>>sites.  However, it seems that the <prepare> section of my conf.xml file
>>has to be set with the same values as I already have in
>>forrest.properties.  Why can't forrestbot just use forrest.properties?
>>
>>Moreover, how to I specify forrest.maxmemory using the
>>forrestbot?  I have it set in forrest.properties, but I get an out of
>>memory error when I run forrestbot.
>>    
>>
>
>The current Forrestbot implementation (XSLT generating Ant) is inflexible
>and convoluted.  Over the last few days I've been rewriting the
>Forrestbot using Ant 1.6's <import> facility.  There's 'get-src', 'site',
>'deploy' and 'notify' targets in a generic script, and each project then
>has a script which overrides key properties.  The targets themselves can
>also be overridden.
>
>It's worked wonderfully well.  *Much* cleaner and more flexible.  Ant's
><import> is a killer feature.
>
>As for your specific question, the generic script <import>'s
>forrest.build.xml, so it does use forrest.properties.
>
>I'll commit my stuff tonight.
>  
>
Jeff,

Is there a reason why you use Ant for this sort of thing, as opposed to 
a more pure Cocoon CLI/bean approach? (other than because the CLI/bean 
isn't good enough yet).

To my mind, this is the sort of thing that I see the CLI/bean doing 
eventually. It can already send pages directly to a modifiable source, 
so with an SCPSource you could remove the final 'copy' stage. There is 
already a CVSSource which can be used to read out of a repository 
(although that would require a change to your sitemap, which is not 
preferable). The cli.xconf can now handle multiple sites (using <uris> 
elements). Then, once the CLI/bean can do all this, it can either be run 
from the command line via cron, or potentially be called from within a 
web interface (run as an Avalon component via the flow).

Can you see the CLI/bean taking over this role at some point in the 
future, or do you think there is some intrinsic role for Ant to play here?

Just musing.