Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 79030 invoked by uid 500); 15 Oct 2002 11:21:31 -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 78946 invoked from network); 15 Oct 2002 11:21:30 -0000 Received: from smtp5.uk.deuba.com (HELO imr5.srv.uk.deuba.com) (160.83.34.38) by daedalus.apache.org with SMTP; 15 Oct 2002 11:21:30 -0000 Received: from sdbo1003.db.com by imr5.srv.uk.deuba.com id g9FBLT6W026492; Tue, 15 Oct 2002 12:21:29 +0100 (BST) Subject: Re: Integrating Forrest with existing Cocoon apps To: forrest-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Michael Edge" Date: Tue, 15 Oct 2002 12:21:28 +0100 X-MIMETrack: Serialize by Router on sdbo1003/DMGUK/DeuBaInt/DeuBa(Release 5.0.9a |January 7, 2002) at 15/10/2002 12:21:29 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: Thanks for the info Marc. It seems that build.xml does not contain a 'dist' target. How do I go about running a 'build dist'? I'm on NT4 by the way. Regards Michael Marc Portier cc: Subject: Re: Integrating Forrest with existing Cocoon apps 15/10/2002 10:48 Please respond to forrest-dev Hi, after running the "build dist" on forrest you should install (copy) the build/dist/shbat into a directory you called FORREST_HOME through some environment variable from then you can use $FORREST_HOME/forrest.sh site in any directory to start forrest-building the documentation there (to a relative dir ./build/site/) the projects that want to hook it up into their existing ant build.xml (like you) can use some target allong the lines of: (as you see the actual forrest-building is done through an underlaying ant script, just try not to get confused by this :-S) when forrest-building your documentation like this it is assumed that your project-home is the current dir (normally the basedir for your build.xml, which is probably what you want) the generated docs would go to ./build/site by default this and other defaults can be modified by using some forrest.properties file that will be picked up by the forrest.build.xml let us know if this theory fails to work in practice :-) HTH -marc= Michael Edge wrote: > Hi again > > I've spent a couple of days trawling through the Forrest and Centipede documentation and, as far as I understand it, Forrest is what we are looking for to document our Cocoon applications. The question is, how do we go about this? We have existing Cocoon apps, complete with ANT build scripts. I need to integrate Forrest into this so that it becomes another target in our build scripts. The current samples generate Forrest documentation, but I can't find any details on how to integrate Forrest with an existing application. > > Any help appreciated. > > Regards > > Michael > > > > -- > > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. > > -- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center mpo@outerthought.org mpo@apache.org -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.