cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans ...@domek.be>
Subject Re: [M10N] cocoon-jcr
Date Wed, 11 Jan 2006 23:19:47 GMT

Giacomo Pati wrote:

> In a big multiproject Maven 1 project we solved this by an entity file
> in the root directory where all dependant jar had entities for their
> groupId, artifactId and version (strictly sorted by groupId and
> artifactId) and each (sub) project.xml file included it and used those
> entity to define their individual dependency. This way we prevented
> version clashes easily and relatively early. This has worked fine (even
> if not recommended by Maven itself. In another project it has hit us
> hard when we used automated integration tests with Continuum which
> wasn't able to locate the entity file anymore because of relative paths
> in the project.xml.


I've never actually used it, but the dependencyManagement [1] element is
all about centrally managing dependency versions.


HTH
Jorg

[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html


Mime
View raw message