Christian Leh wrote:
<include buildfile="dummy.build" checkversion="1.0.5.0" failtask="err" />
A simple approach would be:
<include buildfile="dummy.build.1.0.5.0" />
or more generally
<include buildfile="${build.version}" />I also wonder what causes this need. Either the build file and the file it's trying to include are part of the same version tree under your source control system, or they're not. If they are, there's no way they can be out of sync without somebody doing something funky - which will cause other problems and should not be the norm. If they're not, then the build file should either be responsible for ensuring that the correct version of the separate tree has been checked out or it should be version independent (or both), or possibly it should manage multiple versions - in which case it needs separate paths for them, anyway. We do all three: a master build script is responsible for checking out the right branch (furnished as a command line -D parameter), and it knows how to check out different branches to different directories, but otherwise there's nothing version-specific in the script.
Gary
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
