Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 97092 invoked from network); 15 Jan 2009 19:44:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jan 2009 19:44:50 -0000 Received: (qmail 18335 invoked by uid 500); 15 Jan 2009 19:44:50 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 18276 invoked by uid 500); 15 Jan 2009 19:44:50 -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 Received: (qmail 18267 invoked by uid 99); 15 Jan 2009 19:44:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2009 11:44:50 -0800 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=NORMAL_HTTP_TO_IP,SPF_NEUTRAL,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [81.169.146.180] (HELO mo-p05-ob.rzone.de) (81.169.146.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2009 19:44:41 +0000 X-RZG-CLASS-ID: mo05 X-RZG-AUTH: :I3wBe1Onbu02NkHlDbrpfe8kNG+qAh4Y0eqmCwRzFEVCdcWZt5nnNQOsInVZzw== Received: from [192.168.1.33] (78.Red-83-58-66.dynamicIP.rima-tde.net [83.58.66.78]) by post.strato.de (mrclete mo27) (RZmta 18.10) with ESMTP id k05547l0FIKimV for ; Thu, 15 Jan 2009 20:44:17 +0100 (MET) Subject: Re: SolrForrest plugin From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <496F61F9.7010403@getopt.org> References: <496DC879.3030001@getopt.org> <1232019594.8110.322.camel@eric> <496F3510.7030904@getopt.org> <1232026184.8110.543.camel@eric> <496F4039.5040902@getopt.org> <1232028957.8110.555.camel@eric> <496F61F9.7010403@getopt.org> Content-Type: text/plain; charset=utf-8 Date: Thu, 15 Jan 2009 20:44:16 +0100 Message-Id: <1232048656.2586.24.camel@kenny> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On Thu, 2009-01-15 at 17:19 +0100, Andrzej Bialecki wrote: > Thorsten Scherler wrote: > > >>> Actually did you run "forrest" and not "forrest run". If the page is > >>> link from your pages then it will created static. No extra work no > >>> further configuration. > >> I did run "forrest", and all other static pages have been created. Where > >> should I expect the solr docs? alongside the html/pdf docs? > > > > http://forrest.apache.org/docs_0_90/your-project.html > > > > http://forrest.apache.org/docs_0_90/linking.html > > > > All files that are linked from either > > - site.xml > > - tab.xml > > - anyOtherXmlHavingALinkToTheDoc.html > > are genrated along the e.g. html file in the path they are defined by > > the link. > > Yes, this is clear, but I don't understand how this is relevant to my > question. Does it mean that I should add in > one of my documents? If you want to generate the solr add pages when generating the site then yes every page should have a link to itself but as .solr extension. This way forrest automatically will generate this pages, when generating the rest of the site. > > > > > > If you run forrest in the solr plugin it will actually connect to your > > solr server and inject the documents. > > I don't understand what you're saying - what does it mean to "run > forrest in the solr plugin"? cd whiteboard/plugins/org.apache.forrest.plugin.output.solr/ forrest This will generate the static site. > > > > > You will find index.solr.add in build/site/. > > Apparently I'm still missing some vital step - after building the site I > can see index.html and index.pdf, but no index.solr.add . since you did not added links, right? Are you using the dispatcher or skins? > > > > >>> Makes me curious why you need a static index-creation.solr.add and why > >>> not using http://192.168.0.251:8888/index-creation.solr.add.do directly > >>> and let forrest inject the document. > >> Because I want to control myself when and how the documents are > >> submitted to Solr. > > > > ok, you can do the first one as well with forrest and the second with > > limitation. > > Sorry, this really doesn't answer my question - you assume that I can > keep forrest running and use it to submit Solr documents, which I don't > want to do for various reasons. In such case, is it possible to generate > the Solr docs statically, or not? No, you did not understand. I do not assume a running instance of forrest. When you create your documentation statically the solr server will be updated as well. The dynamic mode allows you to update specific pages. The static the whole bunch. salu2 > > -- Thorsten Scherler Open Source Java