Hi John,
John Casey wrote on Tuesday, June 07, 2005 8:34 PM:
> Starting in maven2, we have two features you might be able to take
> advantage of:
>
> 1. transitive dependency resolution
>
[snip]
>
> 2. <dependencyManagement/> POM section
>
> This new section is meant to be specified in a parent POM
> for your projects, and will help you to manage scope and
> version information for a set of standardized dependencies.
> In other words, if many - BUT NOT NECESSARILY ALL - of your
> projects use servletapi, you can specify an entry in
> <dependencyManagement/> in a common ancestor-POM which
> specifies the version '2.3' for servletapi. Then, when one of
> your projects references servletapi, it need only specify
> <groupId/> and <artifactId/> for that dependency, and the
> version will be retrieved from the <dependencyManagement/>
> section (NOTE: specifying the version locally will override
> the standards defined in the managed information).
> If this doesn't settle your specific issue, feel free to
> refine your question, and we'll do our best to address it.
Can this be redefined in a hierarchy?
super POM: defines 2.3
+ - - parent POM 1: defines 2.4
+ - - child POM 1.1: inherits 2.4
+ - - parent POM 2: inherits 2.3
+ - - child POM 2.1: inherits 2.3
- J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
