Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 19252 invoked from network); 24 Oct 2003 11:13:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Oct 2003 11:13:55 -0000 Received: (qmail 46608 invoked by uid 500); 24 Oct 2003 11:13:50 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 46550 invoked by uid 500); 24 Oct 2003 11:13:50 -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 46537 invoked from network); 24 Oct 2003 11:13:50 -0000 Received: from unknown (HELO out2.smtp.messagingengine.com) (66.111.4.26) by daedalus.apache.org with SMTP; 24 Oct 2003 11:13:50 -0000 Received: from mail.messagingengine.com (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id 2AE2734B829 for ; Fri, 24 Oct 2003 07:13:49 -0400 (EDT) Received: from 10.202.2.150 ([10.202.2.150] helo=mail.messagingengine.com) by messagingengine.com with SMTP; Fri, 24 Oct 2003 07:13:49 -0400 X-Epoch: 1066994029 X-Sasl-enc: tmVoZHjiKvLK1Jd53lVz+A Received: from upaya.co.uk (unknown [213.48.13.34]) by www.fastmail.fm (Postfix) with ESMTP id 2A8B334B825 for ; Fri, 24 Oct 2003 07:13:48 -0400 (EDT) Message-ID: <3F9908EE.9070209@upaya.co.uk> Date: Fri, 24 Oct 2003 12:11:42 +0100 From: Upayavira 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: dev@cocoon.apache.org Subject: Re: Forrest docs in old format. References: In-Reply-To: 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 Carsten Ziegeler wrote: >Upayavira wrote: > > >>I get the CLI to generate /docs/index.html and follow links. If it >>generates the whole site, it gives me a good idea as to how it is >>working, and how fast it is working. >> >>It isn't the best test method, as there are features of the CLI that >>this isn't testing - e.g. link rewriting. I can see that I need a more >>targetted test suite, aimed to show up flaws in these features. >> >>One reason why I haven't done this because I haven't worked out how to. >>Should I just create a sample, or I guess I could add my tests to >>src/webapp/tests/. And have a cli-test.xconf somewhere that can be used >>to run the tests. (I would like to come up with a way to automate the >>checking of the results, but for the time being, checking the resulting >>pages will be a manual process). >> >>Does all this make sense? The better the idea - the easier it'll be for >>me to implement. >> >>Until we've done this, the docs is all I have! >> >> >> >:) > >Now, perhaps I did get something wrong, but as far as I understand >you, you are using the CLI and generate the whole site from the >docs directory. But this has nothing to do with the docs directory >in the build\webapps directory, or am I wrong? > No, to use the CLI, I need a webapp, just like the servlet. And to test the CLI, I need a webapp with some pages in it. Therefore, I use the docs in the webapp (build/webapp/docs/) to test it. >Even if you would use that directory as your source you can >use the src\docs directory. > > We could configure the webapp\docs to use src\docs which would avoid some copying, but I'm not sure if that really helps us all that much. Clearer now? Regards, Upayavira