I think my last post was slightly misleading. I didn't mean to imply it was an ordering issue. The basic problem is that if buildArgs are specified then the targetList doesn't seem to work, only the default target specified in the nant build file is used, not the targets in the targetList. I don't want to call my default target, so even if I combined these 3 target calls into a single ccnet specific target I still wouldn't be able to specifiy the buildArgs because then my ccnet specific target would not get called. Guess I just need to avoid using the buildArgs for now and include the property in the nant build file in the ccnet specific target.
On Dec 4, 5:56 pm, "Adam V." <[EMAIL PROTECTED]> wrote: > This doesn't address the "order of the config file" issue, but I > typically have a "cruise" target that calls other targets in the right > order, so that my CCNet project can call a single target, and if I > need to modify the Nant script behavior I can do it all in the Nant > script without also potentially having to update the CCNet config as > well.
