Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 95598 invoked by uid 500); 22 Jul 2003 12:09:44 -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 94428 invoked from network); 22 Jul 2003 12:09:26 -0000 Received: from fep01.tuttopmi.it (HELO fep01-svc.flexmail.it) (212.131.248.100) by daedalus.apache.org with SMTP; 22 Jul 2003 12:09:26 -0000 Received: from apache.org ([80.204.154.190]) by fep01-svc.flexmail.it (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20030722120854.MCSD1564.fep01-svc.flexmail.it@apache.org> for ; Tue, 22 Jul 2003 14:08:54 +0200 Message-ID: <3F1D28E9.2060203@apache.org> Date: Tue, 22 Jul 2003 14:07:05 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: Directory structure in 0.6 (Re: cvs commit: ...) References: <20030718001723.95409.qmail@icarus.apache.org> <3F173FE7.8090507@che-che.com> <1058529624.3f17e158bca52@secure.solidusdesign.com> <3F17E6BA.1070706@che-che.com> <1058533377.3f17f00190b31@secure.solidusdesign.com> <3F1B7A27.9000105@che-che.com> <1058793879.3f1be997bf162@secure.solidusdesign.com> <3F1BF4C5.1000807@apache.org> <20030722101733.GB3664@expresso.localdomain> In-Reply-To: <20030722101733.GB3664@expresso.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jeff Turner wrote, On 22/07/2003 12.17: ... > Though, the necessity of raw/ is rather annoying, as we still have two > separate content trees with an identical structure. If index.xml refers > to a pregenerated sales.pdf, we'd have: > > src/documentation/content/index.xml > src/documentation/content/raw/sales.pdf > > Perhaps we could rather use marker attributes in site.xml to indicate raw > content: > > > ... > > ... > > > And then just have: > > src/documentation/content/index.xml > src/documentation/content/sales.pdf The issue here was when users wanted to add a large number of raw docs, like javadocs for example. Now, we could also say that in that case we should be able to "mount" other directories as raw or as content, so I could be ok with your solution. I mean, it seems it could be ok, and given my use of the raw dir it is, but would it be so also for other users? -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------