The full error:
[vssget] $/agent/dca3.2 is not an existing filename or project
BUILD FAILED
C:\dca3.2test\testcms.xml:26: Failed executing: "C:\Program Files\Microsoft
Visual Studio\
\win32\ss" Get $/agent/dca3.2 -GLC:\dca3.2test -I- -R -W
I have tried the login, I have a usename but I never need a password hwn
accessinf VSS. I beleive the account info. is thew same(mine).
-----Original Message-----
From: Shannon Wagner [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 11:36 AM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
What's the error that you are getting?
Have you tried also specifying the "login" attribute within the <vssget>
call? I think you need it.
Does the account under which Ant is running have sufficient rights to
\\Ftcollins\FTCOLLINS_D\VSS\COMDev?
-----Original Message-----
From: Dana Rice [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 1:27 PM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
Shannon, I appreciate the help. What I see in VSS explorer above the right
pane is $/agent/dca3.2.
The env.bat looks like:
set ssdir=\\Ftcollins\FTCOLLINS_D\VSS\COMDev
And FTCOLLINS is one of my network places.
<target name="getcode">
<vssget localpath="C:/dca3.2test"
recursive="true"
vsspath="$/agent/dca3.2"
writable="true"
ssdir="C:/Program Files/Microsoft Visual Studio/Common/VSS/win32"/>
<echo message="getcode"/>
</target>
-----Original Message-----
From: Shannon Wagner [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 11:18 AM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
Sorry - I don't know why executing ss.exe brings you into "help".
Yes, we are running "setenv.bat" to set the ssdir variable before each
build.
As for the error you are getting...
[vssget] $/path/to/project/in/vss is not an existing filename or project.
"$/path/to/project/in/vss" needs to be replaced by the VSS path to a
project. For example, you might have a project in VSS like
"$/Java/Applets/Calculator". This is the complete path that you would see
above the right pane if you were browsing to the project using the VSS
explorer.
Why don't you reply with the exact code which you are using, so that I can
see it?
-----Original Message-----
From: Dana Rice [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 1:05 PM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
OK, I wasn't sure because when I execute ss.exe I get into "help". Do you
run you env.bat just before the ant build? I think this is still my problem.
I get this:
[vssget] $/path/to/project/in/vss is not an existing filename or project.
Is \\SERVER\path\to\vss_database
explicitly what is mapped onto your pc?
-----Original Message-----
From: Shannon Wagner [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 10:48 AM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
It should be executing ss.exe, since this is the command line version of the
application. ssexp.exe is just a GUI front-end.
-----Original Message-----
From: Dana Rice [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 12:40 PM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
Thanks Shannon, I'm closer but still not there. Am I wrong in observing that
vssget tries to execute ss.exe? Should it not be ssexp.exe?
-----Original Message-----
From: Shannon Wagner [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 9:49 AM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
Dana,
We're using code similar to the following:
...
rem setenv.bat - This part runs in a batch script.
rem
rem You seem to need to have this environment variable
rem set in order for VSS to find the database.
set ssdir=\\SERVER\path\to\vss_database
...
<!-- build.xml -->
<!-- Note that VSS calls everything a project, not a folder. -->
<vssget localpath="c:\path\to\local\vss\working\folder"
login="vss_user,vss_password"
vsspath="$/path/to/project/in/vss"
ssdir="c:\path\to\vss\executable"
recursive="true"/>
-----Original Message-----
From: Dana Rice [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 11:24 AM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
Thanks for the explanation. I'm having a problem with my vsspath. Part of
the problem is that VSS is on another computer on our network but I still
should be able to get to if I use the correct path statement. What is vssget
looking for? The notes make reference to a project, I usually just get the
latest version, do I have to create a project for vssget to work?
-----Original Message-----
From: Peterson, Lance [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 4:48 PM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
MSVSSGET is the name of the class that implements the vssget task. (The
full name is org.apache.tools.ant.taskdefs.optional.vss.MSVSSGET.)
Defaults.properties (in src/org/apache/tools/ant/taskdefs) maps MSVSSGET to
vssget.
-----Original Message-----
From: Dana Rice [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 4:41 PM
To: '[EMAIL PROTECTED]'
Subject: RE: pulling out the code from SourceSafe
why when you get a listing of the optional.jar there is no vssget but there
is a MSVSSGET?
