What is becoming a real pain about maintaining your script? And how do you
think an Ant task would help?
If you had a reusable build file that did all the pieces, perhaps using
tricks with <antcall> and the ant-contrib <foreach> task you could probably
get by without making a custom task, right?
I'm not trying to sway you from creating a custom task, but only trying to
offer alternatives. Writing a custom task that used the VSS tasks, <ftp>,
and <telnet> would not be that difficult though, and might offer some
benefits.
Erik
----- Original Message -----
From: "Martin Erlandsson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 26, 2002 9:18 AM
Subject: Ant task to map vss folders to actual folders on multiple
machines - exists?
> Hi! A while back I submitted the below request on the user's list, but I
got
> no replies. So, let's try the developers...
>
> TIA,
>
> /Martin
>
> --------------------------------
>
> Hi List.
>
> I am thinking about writing an ant task to automate distribution of
> configuration files from VSS to a number of different configurations
> directories. Before I start, I just want to know if someone has already
done
> something similar???
>
> The mission:
> I use VSS to version-control a bunch of configuration files. When a
> configuration file is changed, it is simply checked in to VSS. Then, an
ant
> script distributes the files to the right place on the right server. This
> ant script uses vss, telnet and ftp tasks to get the files from VSS, set
> permissions and to ftp the files. Also, some files need to be executable,
so
> this is done in the end.
> The thing is, that it is becoming a real pain to maintain this script.
> Consequently, I want to write an ant task to do all this...
>
>
> The task should use something like the following to map the vss path to
the
> actual path:
>
> <mappings>
> <mapping>
> <vsspath>/VSS/path/to/configDir1</vsspath>
> <server>ServerA</server>
> <remotepath>/actual/path/to/configDir1</remotepath>
> </mapping>
>
> <mapping>
> <vsspath>/VSS/path/to/configDir2</vsspath>
> <server>ServerB</server>
> <remotepath>/actual/path/to/configDir2</remotepath>
> </mapping>
> </mappings>
>
>
> Any comments or ideas are appreciated!
>
>
> /Martin
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
