DependencyManagement in a parent pom does not implicitly force the
dependency on every child/module.
You still need to (explicitly) declare the dependency in the children
poms... but you only need to include the groupId and artifactId
because you've already declared the version etc in the depMgmt section
ie:
child.pom
<dependency>
<groupId>third-party</groupId>
<artifactId>dxr-third-party-com-emc-centera-fplibrary-WINDOWS-X86-lib</artifactId>
</dependency>
HTH.
Wayne
On 7/14/06, Brad Harper <[EMAIL PROTECTED]> wrote:
Hello all:
Can anyone say if 'maven-native-plugin' is sensitive to explicit
project dependencies? Should it be?
I have
<dependencyManagement>
<dependencies>
<dependency>
<groupId>third-party</groupId>
<artifactId>dxr-third-party-com-emc-centera-fplibrary-WINDOWS-X86-li
b</artifactId>
<version>2.0SP1</version>
<type>lib</type>
<scope>compile</scope>
</dependency>
</dependencies>
</dependencyManagement>
in a POM descriptor. Sub-projects/modules of this project should
require the named artifact, but
% mvn compile
build successfully, even though I hadn't yet installed the artifact
in the local repository.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
