[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-cocoon-dev
Subject:    Re: [M10N] new block layout
From:       Daniel Fagerstrom <danielf () nada ! kth ! se>
Date:       2005-11-03 17:06:42
Message-ID: 436A43A2.8050207 () nada ! kth ! se
[Download RAW message or body]

Jorg Heymans wrote:

>A standard block layout can look like this :
>
> /cocoon-forms-block
>     pom.xml
>     /api
>        pom.xml
>     /impl
>        pom.xml
>     /samples
>        pom.xml
>
>
>  --> pom.xml
>Is a multimodule pom containing
>
>  <modules>
>    <module>api</module>
>    <module>impl</module>
>    <module>samples</module>
>  </modules>
>
>as well as the dependencies for the block
>    .....
>    <dependency>
>      <groupId>apache-cocoon</groupId>
>      <artifactId>cocoon-ajax-impl</artifactId>
>      <version>2.2-SNAPSHOT</version>
>    </dependency>
>    <dependency>
>      <groupId>jakarta-oro</groupId>
>      <artifactId>jakarta-oro</artifactId>
>      <version>2.0.8</version>
>    </dependency>
>      .....
>
>Note: I'm not 100% sure yet about adding all dependencies at this level,
>this still needs some thought. For now it will do.
>  
>
Would prefer puting API dependencies in the API module and let the impl 
depend on the api and the samples on the impl. Doesn't the tranistive 
dependencies work well enough or what is the reasons for having 
dependencies at parent level?

The rest looks good.

/Daniel

[prev in list] [next in list] [prev in thread] [next in thread]