Jon,
Apparently it works after all. :-) That will teach me to believe the
VSS documentation. It states in the "Remarks" section of the "command
line, label" entry:
The Label command creates a new version of the specified project
or file, and assigns your label to that version.
This most certainly is not happening on my system. It assigns the label
to the current version. Additionally, if I right-click a file in the
VSS GUI and select "Properties..." the label does not show up! This was
really throwing me off. However, the ss history command does reveal
that the label is there. Oh well, thanks Bill!
So I guess all is well and this little diversion had nothing to do with
ant afterall. Thanks again for the help.
Regards,
Dave
-----Original Message-----
From: Jon Skeet [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 5:49 AM
To: [EMAIL PROTECTED]
Subject: RE: VSS Label problems
> Thanks for the response. Here are the relevant parts of the build.xml
> file:
>
> <property name="vss.path" value="\\Puccini\VSS\win32" />
> <property name="project.path"
> value="$/${ant.project.name}/current/implementation" />
> <vsslabel vsspath="${project.path}"
> ssdir="${vss.path}"
> login="${vss.username},${vss.password}"
> label="${build.label}" />
>
> Underneath "implementation" are a number directories (e.g. source,
> database, doc, etc.). When I run this task, only the "implementation"
> directory gets a label. None of the files in this directory
> get a label nor do any of the subdirectories or their files. I can't
> figure it out.
Try taking the $ out from the start of the project path - I certainly
don't use that myself.
Other than that, it all looks okay (my own project needs different
options, eg serverpath but not login/password) but I get all the labels
just fine...
What happens when you try to fetch that label?
Jon
