Bingo. That did it. Thanks.

Brad

-----Original Message-----
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 1:45 PM
To: Maven Users List
Subject: Re: maven-native-plugin sensitive to dependencies? [CORRECTED
SUBJECT LINE]


move it outside of <build>

-D

On 7/14/06, Brad Harper <[EMAIL PROTECTED]> wrote:
>
> I removed the artifact from the repository and modified the POM for
> the child by adding <dependency> within
>
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-native-plugin</artifactId>
>         ...
>         <dependencies>
>           <dependency> ... <--  groupId and artifactId only. no version.
>          ...
>         </dependencies>
>     </plugin>
>    </plugins>
>   </build>
>
> [while leaving the original <dependencyManagement> element in
> the parent].
>
> The child project build was still successful.
>
> Brad
>
> -----Original Message-----
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 14, 2006 11:52 AM
> To: Maven Users List
> Subject: Re: maven-native-plugin sensitive to dependencies? [CORRECTED
> SUBJECT LINE]
>
>
> 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</art
> ifactId>
> </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]
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to