Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 70077 invoked from network); 3 Nov 2004 17:46:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Nov 2004 17:46:27 -0000 Received: (qmail 49885 invoked by uid 500); 3 Nov 2004 17:46:26 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 49762 invoked by uid 500); 3 Nov 2004 17:46:24 -0000 Mailing-List: contact user-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: user@forrest.apache.org Delivered-To: mailing list user@forrest.apache.org Received: (qmail 49707 invoked by uid 99); 3 Nov 2004 17:46:23 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=HTML_30_40,HTML_MESSAGE,NO_REAL_NAME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of peter.dykstra@donovandata.com designates 168.238.130.5 as permitted sender) Received: from [168.238.130.5] (HELO dns2.donovandata.com) (168.238.130.5) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 03 Nov 2004 09:46:22 -0800 Received: from mail.donovandata.com (f5-dmz.wan.donovandata.com [168.238.130.220]) by dns2.donovandata.com (8.12.11/8.12.11) with ESMTP id iA3HkDD0024250 for ; Wed, 3 Nov 2004 12:46:13 -0500 In-Reply-To: To: user@forrest.apache.org Subject: Re: two general questions MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004 Message-ID: From: peter.dykstra@donovandata.com Date: Wed, 3 Nov 2004 12:46:14 -0500 X-MIMETrack: Serialize by Router on SMTP_NY01/USA/DDS(Release 6.5.1|January 21, 2004) at 11/03/2004 12:38:37 PM, Serialize complete at 11/03/2004 12:38:37 PM Content-Type: multipart/alternative; boundary="=_alternative 00619D2685256F41_=" X-Scanned-By: MIMEDefang 2.45 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 00619D2685256F41_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Thanks -- This feature sounds like the answer to my problem. Nicola Ken Barozzi =20 Sent by: news 11/03/2004 11:13 AM Please respond to user@forrest.apache.org To user@forrest.apache.org cc Subject Re: two general questions Thorsten Scherler wrote: > El mi=E9, 03-11-2004 a las 16:04, peter.dykstra@donovandata.com escribi= =F3: ... >>Two general questions: >> >>1. Is there a way to use Forrest to publish a set of files that live >>in a separate place outside of Forrest? The forrest.properties file >>lets me change the directory names and structure, but only within the >>current 'forrest.home' context. The cocoon.xconf settings let me >>override that and point to any location, but then I'm probably >>breaking lots of Forrest functions like search and site links. Is >>there a safe, sanctioned way to keep my content repository in a whole >>separate place, even on a separate server, from the rest of a projects >>files? I'm figuring others may have run into this question, since >>this is a central principle behind Cocoon. >=20 > Search this list and the dev for "IMSManifest". In any case with the locationmap system that is slated for 0.8 it will=20 be possible to mount source directories. >>2. Where's the best place to direct questions about specific skins? >>I've been having a problem with the Tigris skin and have sent two >>notes about it over the last month or two which no one seems to have >>picked up on. If it appears to be a bug, for example, should I be >>sending to a separate list? >=20 > This is the right list for asking thus question. BTW Tigris will not be > supported in future releases of forrest. Hey, if you personally will not support it, it does not mean it will not=20 be supported ;-P It will still be available, don't worrk. --=20 Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --=_alternative 00619D2685256F41_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Thanks -- This feature sounds like t= he answer to my problem.



Nicola Ken Barozzi &l= t;nicolaken@apache.org>
Sent by: news <news@sea.gmane.org= >

11/03/2004 11:13 AM
Please respond to
user@forrest.apache.org
To
user@forrest.apache.org=
cc
Subject
Re: two general questio= ns





Thorsten Scherler wrote:
> El mi=E9, 03-11-2004 a las 16:04, peter.dykstra@donovandata.com escrib= i=F3:
...
>>Two general questions:
>>
>>1. Is there a way to use Forrest to publish a set of files that live
>>in a separate place outside of Forrest? The forrest.properties file
>>lets me change the directory names and structure, but only within the
>>current 'forrest.home' context.  The cocoon.xconf settings let me
>>override that and point to any location, but then I'm probably
>>breaking lots of Forrest functions like search and site links.  Is
>>there a safe, sanctioned way to keep my content repository in a whole
>>separate place, even on a separate server, from the rest of a proje= cts
>>files?  I'm figuring others may have run into this question, since
>>this is a central principle behind Cocoon.
>
> Search this list and the dev for "IMSManifest".

In any case with the locationmap system that is slated for 0.8 it will
be possible to mount source directories.

>>2. Where's the best place to direct questions about specific skins?=
>>I've been having a problem with the Tigris skin and have sent two >>notes about it over the last month or two which no one seems to have
>>picked up on.  If it appears to be a bug, for example, should I be
>>sending to a separate list?
>
> This is the right list for asking thus question. BTW Tigris will not be
> supported in future releases of forrest.

Hey, if you personally will not support it, it does not mean it will not
be supported ;-P

It will still be available, don't worrk.

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------
--=_alternative 00619D2685256F41_=--