Hello all, We may have found an unknown breaking change across nightly builds of 0.85.
With an earlier version of the nightly build, 0.85.1537.0, I was able to use a global fileset for all references for both the <csc> and <uptodate> tasks. Now, with the latest nightly build, I can no longer do this. <csc> expects an <assemblyfileset> for the <references refid="">, while <uptodate> expects a <fileset> for the <sources refid="">. I would expect that the <assemblyfileset> would be implictly upcast to a <fileset> for the <uptodate> task, but, this is not the case. We use <uptodate> twice. The first pass is to compare a fileset of source files and build files against the target binary. The second pass is to compare a fileset of references against the target binary. The theory is that we should only build if any of the following are younger: source CS files, build files (which gen assemblyinfo.cs), or reference assemblies. Simply checking CS files is not enough for a very large application (~100 assemblies/build files). Did the NAnt team intentionally break this feature, or is this a bug? Is there a better way of doing this? Keep in mind that we only want to declare a single fileset for all references, which can be reused across a build file. As always, this product is awesome -- we can't thank you enough for freeing us from VS solution files! Thanks for your help, Steve ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
