Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 31421 invoked from network); 12 Jan 2006 14:36:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jan 2006 14:36:13 -0000 Received: (qmail 91849 invoked by uid 500); 12 Jan 2006 14:36:08 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 91780 invoked by uid 500); 12 Jan 2006 14:36:08 -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 91768 invoked by uid 99); 12 Jan 2006 14:36:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2006 06:36:07 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [195.216.81.147] (HELO mail.otego.com) (195.216.81.147) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2006 06:36:06 -0800 Received: (qmail 16454 invoked from network); 12 Jan 2006 15:35:44 +0100 Received: from 192.168.222.3 by zeus (envelope-from , uid 201) with qmail-scanner-1.25st (clamdscan: 0.87.1/1162. perlscan: 1.25st. Clear:RC:1(192.168.222.3):. Processed in 0.029783 secs); 12 Jan 2006 14:35:44 -0000 Received: from zeus2.otego.com (HELO localhost) (192.168.222.3) by zeus2.otego.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Jan 2006 15:35:44 +0100 Date: Thu, 12 Jan 2006 15:35:36 +0100 (CET) From: Giacomo Pati Sender: giacomo@lapgp.otego.com To: dev@cocoon.apache.org Subject: Re: Block deployment: working with blocks from a user's point of view In-Reply-To: <20060112094456.31051.qmail@web26812.mail.ukl.yahoo.com> Message-ID: References: <20060112094456.31051.qmail@web26812.mail.ukl.yahoo.com> X-GPG-FINGRPRINT: 9E66 40E0 0A9C B37F E29E 5816 2CD7 49BD 98E3 5590 X-GPG-PUBLIC_KEY: http://pks.gpg.cz:11371/pks/lookup?op=get&search=0x2CD749BD98E35590 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 12 Jan 2006, Reinhard Poetz wrote: > Date: Thu, 12 Jan 2006 10:44:56 +0100 (CET) > From: Reinhard Poetz > Reply-To: dev@cocoon.apache.org > To: dev@cocoon.apache.org > Subject: Re: Block deployment: working with blocks from a user's point of view > > > --- Giacomo Pati schrieb: > >> The first thing we need to have is the archetype for >> a block skeleton to >> get a step ahead through the first tutorial. So >> let's define a list of >> items we need and requirements one has. >> >> If I understand your tutorials correctly [1] is >> about creating a single >> block (which _can_ be a single application or a >> brick for build an >> application) > > yes, right > >> and [2] is the creation of a webapp/war >> directory/file >> deployable into a servlet engine. Is this correct? > > yes > > So the next tasks are > > - creating the block archetype > (for the content see [1] "Create your block > skeleton") I'll move the archetypes directory to cocoon-archetypes (to synchronize it with the naming of the other modules) and integrate them into the main cocoon/pom.xml (to make it also easily available in IDEs). I'll create a cocoon-archetype-block in that directory for it. Ok? > - make "mvn cocoon:simple-deploy" work as described > in > [2] "Implicit deployment (of Cocoon block > projects)" > > >> [1] >> > http://cocoon.zones.apache.org/daisy/documentation/g2/796.html >> [2] >> > http://cocoon.zones.apache.org/daisy/documentation/g2/797.html > > -- > Reinhard > > > > > > > ___________________________________________________________ > Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de > > - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDxmlBLNdJvZjjVZARAm3iAJ9ogGjnmBHyKJ+0zd0s6Fdi5Mq1JgCgoKOW YW05/LYFxJ89oyzJht3iqn8= =OZxd -----END PGP SIGNATURE-----