Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 85105 invoked from network); 12 Mar 2005 21:13:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 12 Mar 2005 21:13:25 -0000 Received: (qmail 81277 invoked by uid 500); 12 Mar 2005 21:13:24 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 80914 invoked by uid 500); 12 Mar 2005 21:13:23 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 80888 invoked by uid 99); 12 Mar 2005 21:13:22 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from natpreptil.rzone.de (HELO natpreptil.rzone.de) (81.169.145.163) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 12 Mar 2005 13:13:21 -0800 Received: from 192.168.2.2 (80-28-175-2.adsl.nuria.telefonica-data.net [80.28.175.2]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j2CLDFF4006257; Sat, 12 Mar 2005 22:13:16 +0100 (MET) Subject: Re: Embedding forrest in custom software From: Thorsten Scherler Reply-To: forrest.dev@post.webmailer.de To: forrest dev Cc: forrest user In-Reply-To: <4233343D.2030608@users.sourceforge.net> References: <4233343D.2030608@users.sourceforge.net> Content-Type: text/plain Date: Sat, 12 Mar 2005 22:13:16 +0100 Message-Id: <1110661996.5271.14.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Sat, 2005-03-12 at 20:26 +0200, Arik Kfir wrote: > Hello, > > We are thinking about embedding Forrest as a content generation engine > in our software. Apache lenya is trying to do the same thing. :) I changed the response address to the dev list because we discuss such things in the dev list. ;-) > Currently, the direction we want to take is simply > embedding the Ant runtime itself, and use it to activate Forrest. > > In details we will: > 1. Add the Ant JAR files into our classpath. +1 > 2. Add the xml-forrest.jar to the classpath +1 > 3. Add required JAR files from Forrest's "lib" directory to the > classpath (we're not sure which ones we really need - would appreciate > help on this). That really depends which features of forrest you will going to use. > 4. Create a template project structure (e.g. src/documentation, > forrest.properties, etc) in a temporary directory Why temporary directory? > 5. Activate Ant in code (manually create the Project, etc) to run > Forrest via its standard build.xml file. > you wrote content generation engine, you will use then the normal "forrest"-target you mean? By following this target you will find out which other libs are involved. > Before I start working on this, I was wondering if anyone had any > experience in doing this, or any tips/tricks on the subject. > We are using in the 0.7 plugins to extract additional functionality from the core. Have a look on that. That will give you an idea. HTH > 10x in advance! > Arik Kfir. > > salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)