cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: Why pom.xml and block.xml? (was Re: M10N)
Date Thu, 19 Jan 2006 19:57:10 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 19 Jan 2006, Reinhard Poetz wrote:

> Date: Thu, 19 Jan 2006 17:19:32 +0100
> From: Reinhard Poetz <reinhard@apache.org>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: Re: Why pom.xml and block.xml? (was Re: M10N)
> 
> Upayavira wrote:
>>  Below you explain the role of pom.xml and the role of block.xml. From a
>>  technology point of view, I can see why you are going this way.
>>
>>  However, if we think of a newcomer to Cocoon, I can see this as being
>>  unnecessarily complicated. Why are some things in pom.xml and others in
>>  block.xml? Well, er, because Maven doesn't know how to handle the stuff
>>  in block.xml.
>>
>>  Would it not be possible to put the block.xml data somehow into the
>>  pom.xml file, and have it read by the block deployer mojo?
>>
>>  Even if it were the same info just embedded into the pom.xml file, this
>>  would be substantially more user friendly, IMO.
>>
>>  Does this make sense?
>
> Let's see which information needs to be added to pom.xml:
>
>  - dependencies (block dependencies are different to Maven 2 dependencies)
>  - extension
>  - implementations
>  - servlet (sitemap)
>  - components
>
> Jorg and I have tried to find appropriate places but we were not able to come 
> up with a convincing solution. Maybe somebody else is more successfull ... 
> <hint/>

Could the block.xml be part of the deployer-plugin configuration?

> Well, I would also prefer having only one file instead of two. Having said 
> this I'm not sure if it is really more user friendly because of what we need 
> and what Maven pom.xmls offer. E.g. dependencies have a different meaning in 
> Cocoon than Maven dependencies and the Maven folks have a reason why they 
> don't want to allow dependency properties [1]
>
> Another point is that having a schema for block.xml makes editing very simple 
> because of code completion and validation of XML editors.

This is a good points to have it as a separate file.

> [1] http://docs.codehaus.org/display/MAVENUSER/
> FAQs#FAQs-WhytherearenodependencypropertiesinMaven2%3F

- -- 
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)

iD8DBQFDz+8YLNdJvZjjVZARAh4JAKDSRB1l80O3Hd5sQCi/beIa/GJm8gCfdo8W
pbNH27RkKCQ+Ewv4cZw1RRg=
=vJ04
-----END PGP SIGNATURE-----

Mime
View raw message