I will have target name collision if I do that. There exist a common set
of targets in all my build files such as build, clean, test, etc. I
could rename the targets in every file to be more like projectA.clean,
projectA.build, projectA.test, etc. However, this makes it a little less
intuitive for the user when they wish to execute a build file. They must
do:
NAnt projectA.clean
Instead of just
NAnt clean
Is this a reasonable approach? Thanks.
-Andy
-----Original Message-----
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 25, 2004 11:57 PM
To: Andy Harris
Cc: NAnt Users List (E-mail)
Subject: Re: [Nant-users] [Fwd: Multi build file dependancies]
>
>
> I enjoy using NAnt for our build process, but am having trouble with
the
> concept of dependencies across build files. My original plan was to
have
> n build files, but a build target in one is dependant on build targets
> of other files. I don't see how these dependencies can be accomplished
> across build files. I suppose I am back to putting all projects in one
> huge NAnt build file, but this does not seem modular to me. Any help
> would be appreciative.
>
>
Hi Andy,
You can make a target dependent on targets defined in other files if you
include them via the <include> task.file
so
file1:
<project name="foo">
<target name="A" >
...
</project>
file2
<project name="main" >
<include buildfile="file1.build" />
<target name="B" depends="A" >
...
</project>
Ian
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
