[nant-dev] RE: [Nant-users] 0.85 release candidate by August 4th

2004-07-23 Thread Noel Gifford
Malcolm or anyone else having questions about building, I hope this helps. I do the following: 1) Install the NAnt zip into directory ( C:\Projects\NAnt-0.85-20040722 ) 2) Install the NAntContrib zip into directory ( C:\Projects\NAntContrib-0.85-20040723 ) 3) Build the NAnt by going to its

Re: [nant-dev] ResourceFileSet

2004-07-23 Thread Ian MacLean
First off sorry for top-posting but this thread is getting too long to reply inline. I agree that having a profusion of resource related elements isn't a good thing so lets go with the augmented fileset rather than a dedicated element. Now just to be clear on what we are going to need in terms

[nant-dev] Re: [Nant-users] 0.85 release candidate by August 4th

2004-07-23 Thread Ian MacLean
Malcolm MacLucas wrote: Ok first, I a mistake in my original post, there is no 7-23 build of nant, there is a 7-22 build, that's the one I used. I used the 7-23 build of NAnt Contrib. I installed it into the previously mentioned program files\nant directory and the I ran the NantContrib.build nant

[nant-dev] Re: [Nant-users] 0.85 release candidate by August 4th

2004-07-23 Thread Ian MacLean
Malcolm MacLucas wrote: I'm in the process of setting up a machine just for (currently) NAnt testing, so I'll see what I can do, but I'm more interested in using my time to support a August 4 release, or at least candidate release for Nant 0.85 Currently I'm trying to get a copy of the 7-23 NAnt Bu

Re: [nant-dev] ResourceFileSet

2004-07-23 Thread Gert Driesen
- Original Message - From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Cc: "Nant-Developers (E-Mail)" <[EMAIL PROTECTED]> Sent: Friday, July 23, 2004 5:46 PM Subject: Re: [nant-dev] ResourceFileSet > Gert Driesen wrote: > > >I think we need to add a child e

Re: [nant-dev] ResourceFileSet

2004-07-23 Thread Ian MacLean
Gert Driesen wrote: I think we need to add a child element that would allow the manifest resource name of a given resources file to be explicitly set. I agree. As you say below, having to copy files to specify an explicit name isn't ideal. We actually need this ourselves in several places : -

[nant-dev] [ nant-Bugs-996454 ] NAnt build error

2004-07-23 Thread SourceForge.net
Bugs item #996454, was opened at 2004-07-23 12:45 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=996454&group_id=31650 Category: Tests Group: 0.84-rc1 >Status: Closed >Resolution: Fixed Priori

[nant-dev] [ nant-Bugs-996454 ] NAnt build error

2004-07-23 Thread SourceForge.net
Bugs item #996454, was opened at 2004-07-23 12:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=402868&aid=996454&group_id=31650 Category: Tests Group: 0.84-rc1 Status: Open Resolution: N

[nant-dev] ResourceFileSet

2004-07-23 Thread Gert Driesen
Ian, I think we need to add a child element that would allow the manifest resource name of a given resources file to be explicitly set. We actually need this ourselves in several places : - : right now, we're forced to pass embedded resources from CompilerBase to the task as command line argu