We avoid the problem completely (in part because we were rushed to get the
system in place) by starting with a fresh directory tree. The only problem
that we've had is keeping users out of the build tree on our build machine
when a new one starts otherwise <delete dir="${root}"/> fails. We solved
that problem by adding publishing targets once the build is complete.
>From my perspective, the VSSGET task is doing the RightThing when failing on
a writable file in the build tree, even if it is a little inconsistent.
This because you never want someone doing a check-out into your build tree.
(We also avoid specifying a drive letter so that developers can have a local
instance of the build environment on their favorite drive without impacting
the build machine.)
--
[EMAIL PROTECTED]
Sr. Software Engineer
Broadband Solutions Group
Sony Electronics, Inc.
San Jose, CA
1-408-955-4962
> -----Original Message-----
> From: Jim Urban [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 30, 2001 11:44 AM
> To: [EMAIL PROTECTED]
> Subject: VSSGET Problem
>
> We are using Ant to build a Java web application. We use MS VSS for
> source management. We are trying to use the vssget option to get the
> latest copy of each of our Java source files (<vssget
> localPath="${src}/com/xxx/yyy" recursive="false" vsspath="$/OUR_PROJ/Web
> Apps/Java/*" writable="false"/>). The way the get function works, if a
> write able copy of the file exists in the working directory, the file is
> not fetched and an informational message is issued. The problem is, when
> this happens, Ant says vssget failed and the build stops. How can I tell
> ant to continue if the vssget fails? I am looking for something like the
> failonerror option of the Ant task javac.
>
> Thanks, We love Ant, its so much easier to use then make.
>
> Jim Urban
> Product Manager
> Netsteps Inc.
> Suite 505E
> 1 Pierce Pl.
> Itasca, IL 60143
> Voice: (630) 250-3045 x2164
> Fax: (630) 250-3046
>
