I downloaded v1.4.1160.25852 (the most recent pre-beta) of
the client and it still exhibits the same problem against the server that's
running (v1.4.1223.9059 - which doesn't match anything on the project page for
some reason). When the crew
goes home, I'll install another server with the
My question for Chuck & Co. is "You're already using NAnt. Why not use
the vssget task that's built into NAnt to put the source exactly where
you want it?"
Draco is great for watching VSS and firing a NAnt script which takes
care of all of its own care and feeding (deleting everything the working
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 possible build - without relying on
'clean' targets in the build script to be implemented correctly.
So Ervs solution of
This
has been discussed, but I don’t know what the timeline will look like.
In
the mean time, a common solution is to put your nant script *in* VSS with
your code and then have it work off of purely relative paths.
From: Chuck Bryan
[mailto:[EMAIL PROTECTED]
Sent: Friday, N
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
Due to the increased amount of spam that is appearing on the mailing
lists, I have changed the list options to prevent posting from anyone
other than list members.
Hopefully we won't need to start approving membership next!
-Mark
---
This SF
