-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 5 Jan 2006, Antonio Gallardo wrote:
Date: Thu, 05 Jan 2006 11:24:40 -0600
From: Antonio Gallardo <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [VOTE] green light for flattening repo structure in trunk
Jorg Heymans wrote:
Vadim Gritsenko wrote:
> Jorg Heymans wrote:
>
>
> > [ +1 ] flatten the structure and pave the way for a 2.2 release
> >
> >
>
> Minor point: does it have to be 'cocoon-core', 'cocoon-webapp',
> 'cocoon-<blockname>'; could it be 'core', 'webapp', 'block-<blockname>'?
> Not sure it will be easy to navigate among all those 'cocoon-foo's :)
>
>
>
Matching the directory name with the artifactId is recommended practice.
I can't exactly remember the benefits, but i know it saves extra
configuration in reactor builds eg when using continuum.
Should not be due name collision. ie: a core.jar released in another project?
Yes, I will prefer to keep a prefixed name as cocoon-core.jar. No matter
where we find this file, his names states it is the cocoon core.
There is a project/build/finalName element in the pom.xml to define the
artifact name.
- --
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)
iD8DBQFDvZZALNdJvZjjVZARApo1AKCvMTgUt84IB81HisOwHqS7AC/6NgCcCYeo
qv1TSElVNyj5W9EbMBZVtpc=
=khdX
-----END PGP SIGNATURE-----
