I have a number of targets of various type (code compilers, file system
management, custom scripts) and I'd like to separate them out into
individual files and reference them from a master build file. I thought the
<include> task would meet my requirements, but since it executes the targets
in the included build file whenever the <include> task is touched, it does
not.
What I would like to be able to do is something like this:
<project name="...">
<!-- Global Properties -->
<include buildfile="globals.build" />
<!-- Scripted target collection -->
<include buildfile="scripts.build" />
<target name="build">
<!-- 'myFunkyLittleScriptTarget' is
defined in scripts.build -->
<call target="myFunkyLittleScriptTarget" />
</target>
</project>
In the current model, all the targets in scrips.build would get called and
the <call> task would try to invoke a target that is not defined. Has anyone
any thoughts on how I can achieve my goal?
--Neil
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
