Kenney Westerhof wrote:
[snip]
The meaning of depMgt is different, applied to either local deps or
transitive deps, and it's not consistent.
This somewhat describes the situation:
- depMgt for artifact X is used to provide defaults for direct
dependencies of artifact X,
and for
I think you're questioning if you have this:
dependencyManagement
dependencies
dependency
artifactIdfoo/artifactId
groupIdcom/groupId
version1/version
/dependency
/dependencies
/dependencyManagement
dependencies
dependency
artifactIdfoo/artifactId
groupIdcom/groupId
Kenney Westerhof wrote:
Hi,
Just did some test wrt MNG-2340 (using maven 2.0.7 and 2.0.6), and this is
what I found:
P with dependencyManagement for lucene 1.3
|
+ my-dep with dependency on lucene 1.4.3
+ my-app with dependency on my-dep
(I modified the attached project locally;
Kenney Westerhof wrote:
This somewhat describes the situation:
- depMgt for artifact X is used to provide defaults for direct
dependencies of artifact X,
and for overrides of transitive dependencies on X,
unless there's also a direct dependency on X in which case the direct
dependency is
Brian E. Fox wrote:
I think you're questioning if you have this:
dependencyManagement
dependencies
dependency
artifactIdfoo/artifactId
groupIdcom/groupId
version1/version
/dependency
/dependencies
/dependencyManagement
dependencies
dependency
artifactIdfoo/artifactId
Ralph Goers wrote:
Kenney Westerhof wrote:
This somewhat describes the situation:
- depMgt for artifact X is used to provide defaults for direct
dependencies of artifact X,
and for overrides of transitive dependencies on X,
unless there's also a direct dependency on X in which case the
