-Original Message-
From: David Reed [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 12:45 PM
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] VSS Working Directory
My question for Chuck & Co. is "You're already using NAnt. Why not use
the vssget task that's built i
AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Draconet-users] VSS Working Directory
>
> Hi
>
> Just to give a bit of background info: Draco was intentionally
designed
> to operate from a freshly checked out copy of the codebase. This
> ensures that you get the cleanest p
ay, November 07, 2003 9:49 AM
To: [EMAIL PROTECTED]
Subject: [Draconet-users] VSS Working Directory
This is probably obvious, and something that I have missed.
My Nant build script looks at a directory where I normally "Get Latest"
to, and perform using the source files in that directory
, November 07, 2003 9:49 AM
To: [EMAIL PROTECTED]
Subject: [Draconet-users] VSS Working Directory
This is probably obvious, and something that I have missed.
My Nant build script looks at a directory where I normally
“Get Latest” to, and perform using the source files in that
directory
Hello Chuck,
Are you using absolute paths in your NAnt file?
If so, you may want to make your script portable by using relative
paths. The build script of NAnt is an example of this.
Example: Project.build located in D:\ProjectRoot\ contains a path
"D:\ProjectRoot\build".
Solution: Change thi
Chuck,
If you build your NAnt script such that paths are relative, it should all work fine.
If you have
Draco running on some server, the model is that everything needed to build must be
within the VSS
project, and be relative. However, if you needed to install something outside of this
const
This is probably obvious, and something that I have missed.
My Nant build script looks at a directory where I normally “Get
Latest” to, and perform using the source files in that directory
structure. With Draco, it appears that it puts the files in a temp directory,
which my Nant script
