From forrest-dev-return-7650-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org Thu Oct 02 09:05:37 2003 Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 44156 invoked from network); 2 Oct 2003 09:05:37 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Oct 2003 09:05:37 -0000 Received: (qmail 16561 invoked by uid 500); 2 Oct 2003 09:05:08 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 16428 invoked by uid 500); 2 Oct 2003 09:05:07 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 16213 invoked from network); 2 Oct 2003 09:05:06 -0000 Received: from unknown (HELO grunt26.ihug.com.au) (203.109.249.146) by daedalus.apache.org with SMTP; 2 Oct 2003 09:05:06 -0000 Received: from p214-tnt6.syd.ihug.com.au (expresso.localdomain) [203.173.146.214] by grunt26.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 1A4zOf-0006p3-00; Thu, 02 Oct 2003 19:05:18 +1000 Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian)) id 1A4zRx-0005b2-00 for ; Thu, 02 Oct 2003 19:08:41 +1000 Date: Thu, 2 Oct 2003 19:08:41 +1000 From: Jeff Turner To: forrest-dev@xml.apache.org Subject: Re: [RT] CLI and Forrestbot (was Re: New Forrestbot in the works (Re: forrestbot configuration)) Message-ID: <20031002090841.GC14669@expresso.localdomain> Mail-Followup-To: forrest-dev@xml.apache.org References: <20030930224446.GA31518@minotaur.apache.org> <3F7AAC89.7040606@upaya.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F7AAC89.7040606@upaya.co.uk> User-Agent: Mutt/1.5.4i 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 Wed, Oct 01, 2003 at 11:29:29AM +0100, Upayavira wrote: > 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 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 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 > > is a killer feature. > > > >As for your specific question, the generic script '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 > 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? Well where does the CLI's job begin and end? Its contract seems pretty clear to me; it wants a directory of content and cocoon.xconf file, and spits out a bunch of content. But there are jobs to do before and after that. Before: - Collate or generate content to be included in the site. For Cocoon this means copying lib/jars.xml to src/documentation/xdocs/. It might mean invoking Javadoc, or invoking Maven targets to generate all those pointless stats people love. All far too general for the CLI to do. - More mundanely, obtain a project's static XML from somewhere (CVS, scp, ftp). You're right, this could be done, slowly (opening a ssh connection for each file I imagine), with a CVSSource. After: - Notify someone of the render status (via email, , sms etc). - Publish the results (local copy, scp, ftp). Most of that seems more suited to Ant than the Cocoon CLI. --Jeff > Just musing. > > >