-----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 <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]> 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-----
