Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 59648 invoked from network); 21 May 2004 05:50:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 May 2004 05:50:02 -0000 Received: (qmail 75584 invoked by uid 500); 21 May 2004 05:50:34 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 75491 invoked by uid 500); 21 May 2004 05:50:33 -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 75418 invoked by uid 98); 21 May 2004 05:50:32 -0000 Received: from nick@chalko.com by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(66.60.148.34):. Processed in 0.019637 secs); 21 May 2004 05:50:32 -0000 X-Qmail-Scanner-Mail-From: nick@chalko.com via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(66.60.148.34):. Processed in 0.019637 secs) Received: from unknown (HELO csm.chalko.com) (66.60.148.34) by hermes.apache.org with SMTP; 21 May 2004 05:50:32 -0000 Received: from [127.0.0.1] (unknown [192.168.57.233]) by csm.chalko.com (Postfix) with ESMTP id EE1B61003E for ; Thu, 20 May 2004 22:49:47 -0700 (PDT) Message-ID: <40AD9892.40604@chalko.com> Date: Thu, 20 May 2004 22:50:10 -0700 From: Nick Chalko User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: [Forrest 0.6] Disabled forrest.antproxy.xml --> How to integrate Forrest in Ant build file? References: <40AA0A97.4080203@apache.org> <40ACE817.7040206@brondsema.net> In-Reply-To: <40ACE817.7040206@brondsema.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The problem is that forrest uses some pretty common property names which might conflict with what a uses already has in his build.xml see http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-145 A solution I use at work is to create a ant macro for forrest that fork a new ant on forrest.build.xml I will post a sample macro tomorrow from work. > > Actually if you don't want any of the forrestbot features (getsrc, > deploy, notify, etc) you can import forrest.build.xml instead of the > forrestbot. Then the 'site' target and any other forrest target can > be used in your project. Here's a very small example, let me know if > you need more explanation (somebody remind me to put this as a FAQ...) > > > > > > > > hello > > > > > something here > > > >