[nant-dev] Bug #908317 - Project with no source files builds with an error

2004-03-03 Thread Keyser, Jeffrey
Gert, I'm answering your question in the mailing list rather than the bug itself because I think my answer may prompt a larger discussion. First, let me describe our situation - We have a VS.NET solution that was created before I started here. One of the projects is a documentation-only project

[nant-dev] [ nant-Bugs-908317 ] Project with no source files builds with an error

2004-03-03 Thread SourceForge.net
Bugs item #908317, was opened at 2004-03-02 15:21 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=908317&group_id=31650 Category: Tasks >Group: 0.85 Status: Open Resolution: None Priority: 5 Su

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Giuseppe Greco
Currently, targets in master build files look like this: ... ... Then, if the NAnt group decides to accept this my proposal, targets in master build files will look like this: ... ... ... and gateway build files like this:

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Matthew Mastracci
Giuseppe Greco wrote: As a curiousity, wouldn't you be able to use a regular target and properties to define what to call? For instance, your gateway project can just do this: Yes, but this is exactly what I'm trying to avoid... When a master build file contains more than 3 or 4 targets to forw

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Giuseppe Greco
> As a curiousity, wouldn't you be able to use a regular target and > properties to define what to call? For instance, your gateway project > can just do this: > >name="process" > description="Builds recursively all subprojects"> >item="Folder" > property=

[nant-dev] Re: Wild targets/Current target

2004-03-03 Thread Matthew Mastracci
As a curiousity, wouldn't you be able to use a regular target and properties to define what to call? For instance, your gateway project can just do this: The master just needs to set the "o

[nant-dev] Wild targets/Current target

2004-03-03 Thread Giuseppe Greco
Hi all, I've just completed the implementation of the stuff we discussed yesterday. Right now I'm out of office and I don't have CVS access due to proxy restrictions, so attached to this email you will find the modified files. I'll send you a patch tomorrow. The modified files are: NAnt.Core/Pr

[nant-dev] [ nant-Bugs-908317 ] Project with no source files builds with an error

2004-03-03 Thread SourceForge.net
Bugs item #908317, was opened at 2004-03-02 09:21 Message generated for change (Comment added) made by c-jkeyser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=908317&group_id=31650 Category: Tasks Group: 0.84-rc1 Status: Open Resolution: None Priority:

[nant-dev] [ nant-Bugs-902858 ] Internal Error When Try To Create An MSI That Uses A Vdproj

2004-03-03 Thread SourceForge.net
Bugs item #902858, was opened at 2004-02-23 18:49 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=902858&group_id=31650 Category: Tasks Group: 0.85 >Status: Closed Resolution: Works For Me Prio

[nant-dev] [ nant-Bugs-902858 ] Internal Error When Try To Create An MSI That Uses A Vdproj

2004-03-03 Thread SourceForge.net
Bugs item #902858, was opened at 2004-02-23 17:49 Message generated for change (Comment added) made by ianrow You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=902858&group_id=31650 Category: Tasks Group: 0.85 Status: Open Resolution: Works For Me Priority: