Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 12131 invoked from network); 11 Dec 2003 22:30:47 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Dec 2003 22:30:47 -0000 Received: (qmail 14661 invoked by uid 500); 11 Dec 2003 22:30:33 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 14625 invoked by uid 500); 11 Dec 2003 22:30:32 -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 14613 invoked from network); 11 Dec 2003 22:30:32 -0000 Received: from unknown (HELO www2.kc.aoindustries.com) (65.77.211.84) by daedalus.apache.org with SMTP; 11 Dec 2003 22:30:32 -0000 Received: from dialup-165.146.220.203.acc01-aubu-gou.comindico.com.au (dialup-165.146.220.203.acc01-aubu-gou.comindico.com.au [203.220.146.165]) (authenticated) by www2.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id hBBNVse30053 for ; Thu, 11 Dec 2003 17:31:54 -0600 Subject: Re: [RT] custom skin in multiple projects From: David Crossley To: forrest-dev@xml.apache.org In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1071181832.1237.33482.camel@ighp> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 12 Dec 2003 09:30:33 +1100 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 Dave Brondsema wrote: > With my work on forrestbot and the current discussion of custom skins I > realized I will want to use one custom skin for many projects. I don't > think it's fitting to put it in the Forrest package, nor to put it in all > the projects' src directories. > > I'd like to be able to have an external location (any specified directory) > that forrest will look for skins. Is this a good idea? Can this achieved by the recently added "fetch-skins" task? Perhaps it can first look for a local "skins descriptor" file. --David