Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 28277 invoked from network); 19 Jan 2006 15:24:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Jan 2006 15:24:55 -0000 Received: (qmail 62326 invoked by uid 500); 19 Jan 2006 15:24:40 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 62166 invoked by uid 500); 19 Jan 2006 15:24:39 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 62111 invoked by uid 99); 19 Jan 2006 15:24:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2006 07:24:38 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.11.95] (HELO smtp006.mail.ukl.yahoo.com) (217.12.11.95) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 19 Jan 2006 07:24:37 -0800 Received: (qmail 23995 invoked from network); 19 Jan 2006 15:24:15 -0000 Received: from unknown (HELO ?84.20.186.135?) (reinhard?poetz@84.20.186.135 with plain) by smtp006.mail.ukl.yahoo.com with SMTP; 19 Jan 2006 15:24:14 -0000 Message-ID: <43CFAF1A.2040602@apache.org> Date: Thu, 19 Jan 2006 16:24:10 +0100 From: Reinhard Poetz User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: M10N References: <43CDEB1C.6000002@apache.org> <43CE09B5.6020406@apache.org> <43CE18A8.8040800@apache.org> <43CF5342.4000103@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Giacomo Pati wrote: >> I hope that I can provide a first useable version of the >> deployer-maven-plugin by the end of the week so that you (and others) >> can try it out and that we find a balance between what should be >> configureable and what not, which and how many configuration files we >> want, what they actually configure and how they relate to each other. > > > Ahem.. I was working on the plugin for the simple-deploy goal. Are we > stepping on each others toes? yep ;-) I send you my initial implementation in a separate mail. Maybe you can check in your changes by tommorrow morning so that I can have a look at it tommorrow. > What is the element in the block-deploy.xml for and how should > the simple-deploy goal satisfy that. Well, the Cocoon element is in flux. My goal is that it contains - the target location (Where is Cocoon installed?) - a webapp skeleton - at least a web.xml we need in the case of cocoon:dev-deploy - a version as deployment could change in the future (to be future-safe) - does deployment remove all existing blocks (attribute "exclusive") Currently the skeleton attribute is missing and needs to be added to the schema. The content is something like "org.apache.cocoon:cocoon-webapp-skeleton:1.0" and can be resolved by the ArtifactFactory/Resolver of Maven. HTH -- Reinhard P�tz Independent Consultant, Trainer & (IT)-Coach {Software Engineering, Open Source, Web Applications, Apache Cocoon} web(log): http://www.poetz.cc -------------------------------------------------------------------- ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de