Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 51290 invoked from network); 14 May 2007 22:43:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 May 2007 22:43:53 -0000 Received: (qmail 61864 invoked by uid 500); 14 May 2007 22:43:59 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 61821 invoked by uid 500); 14 May 2007 22:43:59 -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 List-Id: Delivered-To: mailing list dev@forrest.apache.org Delivered-To: moderator for dev@forrest.apache.org Received: (qmail 26498 invoked by uid 99); 14 May 2007 22:21:42 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Date: Mon, 14 May 2007 15:21:14 -0700 (PDT) From: Chris Hostetter To: Solr Dev Cc: forrest dev Subject: Re: [jira] Commented: (SOLR-238) [Patch] The tutorial on our website is against trunk which causes confusion by user In-Reply-To: <1179178382.28992.25.camel@cartman> Message-ID: References: <31518082.1179166816748.JavaMail.jira@brutus> <1179178382.28992.25.camel@cartman> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org : To understand it right you would like to build the site with forrest and : in the build appears the version number and the name of the dis (ant : property ${fullnamever}) of the tutorial. actually, i was just wondering about generic property replacement when converting from the raw source docs to the HTML/PDF docs using a proeprty file ... i was assuming this file could be generated by the build.xml -- so even if ant isn't what kicks off forrest (we currently don't have it setup that way) forrest would load the key/value mappings from a property file generated by the last ant build. : One idea was for me to use a filter with the copy task that e.g. : @fullnamever@ will be substitute with ${fullnamever}. The problem is : that would not be substituted then on the live website. the live site is currently upated manually by developers, anytime a change is commited to the site dir ... so we can make sure the site is updated anytime it needs to be if there is a simple process. but in general i'm not excited by the prospect of solving this problem using an ant copy filter because that doesn't help when deves are previewing how the site will look using forrest, as you say ... : One could replace http://wiki.apache.org/solr/Website_Update_HOWTO step : 2 of "Website update steps" with a target that is doing the filtering : for you. Then in "forrest run" you would find @fullnamever@ but after : building the site and using the copy target with filtering true you have : the variable substituted. The problem is that the nightly builds would that's why i was hoping forrest had a variable substitution mechanism built into it that could just read from some file that we have ant generate. : need to build as well the documentation with forrest. Letting forrest do : the substitution and import forrest targets into the solr build.xml is a : similar approach but then you have an even bigger dependency on forrest. as i say, i don't think the build.xml needs to depend on Solr (the nightly builds don't currently regen the site) ... we just need the build.xml to produce a property file or something like it (easy to do) and we need forrest to read that file and fill in variables with the values it finds. is there something like that in forrest? -Hoss