nant-developers  

[nant-dev] [ nant-Bugs-975396 ] uptodate breaking change

SourceForge.net
Fri, 18 Jun 2004 09:11:22 -0700

Bugs item #975396, was opened at 2004-06-18 16:42
Message generated for change (Comment added) made by drieseng
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=975396&group_id=31650

Category: Core
Group: 0.85
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: stj3570 (stj3570)
Assigned to: Nobody/Anonymous (nobody)
Summary: uptodate breaking change

Initial Comment:
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
<uptodatetasks>.

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.



----------------------------------------------------------------------

>Comment By: Gert Driesen (drieseng)
Date: 2004-06-18 18:03

Message:
Logged In: YES 
user_id=707851

This is now fixed in cvs.

You can now define a "global" <assemblyfileset>, and use this 
in both the <csc> and <uptodate> tasks.

Thanks for the report !

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=975396&group_id=31650


-------------------------------------------------------
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
  • [nant-dev] [ nant-Bugs-975396 ] uptodate breaking change SourceForge.net