Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 54964 invoked from network); 15 Feb 2005 07:54:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Feb 2005 07:54:12 -0000 Received: (qmail 20908 invoked by uid 500); 15 Feb 2005 07:54:09 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 20803 invoked by uid 500); 15 Feb 2005 07:54:09 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 20789 invoked by uid 99); 15 Feb 2005 07:54:09 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of melowe@gmail.com designates 64.233.184.201 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.201) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 14 Feb 2005 23:54:08 -0800 Received: by wproxy.gmail.com with SMTP id 55so2758680wri for ; Mon, 14 Feb 2005 23:54:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=VYNDqSUF8tbCzO3QhUam1tro/W1c3WTYdOrW9nI5hrqf8qXwbN64F7unnNYfjzWdPVaIugSkDuU+UdXUq3IlEMYqQi/ktVItYm7dp8aVUR6yoMSj/Gu0f+4hIuY82g7bgsR3kIyIiGm3eSz/l75dNIJhoLl+dJaycZD3LOdj5Uw= Received: by 10.54.45.11 with SMTP id s11mr71195wrs; Mon, 14 Feb 2005 23:54:05 -0800 (PST) Received: by 10.54.27.42 with HTTP; Mon, 14 Feb 2005 23:54:05 -0800 (PST) Message-ID: <3e1257da05021423541715517b@mail.gmail.com> Date: Tue, 15 Feb 2005 08:54:05 +0100 From: Mark Lowe Reply-To: Mark Lowe To: dev@cocoon.apache.org Subject: Building webapp resources Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello My appologies for asking aquestion not directly related to the development of cocoon but I need some authoritive input on an issue. I'm working on a project where my predecesors deemed it nessesary to have individual build processes for each sub directory/module in the webapp. The build process does nothing more than merge various sitemap fragments into a a single sitemap file. There's little to be gained and the rationalisation could/should take place by using the sitemap heirarchy rather than merging like this. Now my question is what views do you have regarding this sort of nonesense. To my mind while MVC might be maintained in terms of the where all the code is and how it interacts, the practical implications are that a site builder/editor cant work on the resources without building the project. I'd like to confirm that cocoon developers consider it good practice to have the web app resources as relativly static and inituitive for site builders/editors to work on non java stuff without getting bogged down in crack induced sub builds. Again I know this isn't a cocoon dev question but your input will be invaluable. Mark