ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zak Saurin" <zak.sau...@netsystechnologies.com>
Subject RE: ClearCase updates
Date Thu, 15 Nov 2001 10:29:44 GMT
Ah I see!  At the moment I just ensure that the load rules are the
same for all config specs used in the build, but I also like your
idea.

I would be interested in seeing (and using) the scripts and ant
files, if you care to post them on the list.

If the java development of an optional task goes well (I'm
referring to the response by Stephane Bailliez) that would
be the best solution of course.  Maybe the task could be programmed
to provide a default of yes to the unload questions, rather than
do what the script does (which is a nice work around ;-) )

Thank you very much for your input.  It's nice to know that I don't
suffer alone!!

Zak Saurin.

> -----Original Message-----
> From: Anthony Rodriguez [mailto:Anthony@WeddingChannel.com]
> Sent: 14 November 2001 17:55
> To: 'Ant Users List'
> Cc: 'zak.saurin@netsystechnologies.com'
> Subject: RE: ClearCase updates
>
>
> Zak:
>
> I've had to deal with this annoying ClearCase problem as
> well.  It is an
> issue with setcs and snapshot views.  The setcs command asks
> for user input
> when the new config spec being used has different load rules
> from the old
> config spec.  It then prompts the user for a yes or no for
> unloading VOBs.
> After many hours of phone calls and email tag with Rational,
> I came up with
> a solution myself.  My workplace uses snapshot views to build and view
> profiles to make new views.
> I created a task in ant called setcs.  It's basically an exec
> task that
> first calls a perl script that I wrote called setcs.pl.  This
> script goes to
> the view storage dir (*.vws dir) of the view I want change
> and reads the
> load rules from the old config spec file into an array.  It
> then goes to the
> directory of the new view profile I want to use, and copies
> the "Rules" file
> into the view storage dir (renaming it to "config spec").  It
> then appends
> the old load rules to the new config spec file, thereby
> ensuring the same
> load rules as the previous config spec meaning no user input
> when I run
> setcs.  After the perl script is done, the setcs task in Ant execs the
> cleartool setcs -current command.  This reads in the new
> config spec and
> updates the view accordingly.
> I know it's a bit of a perl hack, but it's been working for
> me really well.
> If people are interested, I could post a copy of the perl
> script and ant
> task I use.  But it would probably be cooler if a Java guru
> out there could
> write a class/optional task that could do this.
>
> -Anthony
>
> > -----Original Message-----
> > From: Zak Saurin [mailto:zak.saurin@netsystechnologies.com]
> > Sent: Wednesday, November 14, 2001 6:43 AM
> > To: Ant User List (E-mail)
> > Subject: ClearCase updates
> >
> >
> > I see that there are already tasks created to deal with some very
> > fundamental ClearCase interactions, one of them being an update.
> >  
> > However, I am after a task in which you can specify a config
> > spec and *then*
> > do an update.  Has anybody written such as task?
> >  
> > In the meantime I have tried using the equivalent exec
> > command instead (the
> > DOS command is "cleartool setcs <filename>").  Thie presents
> > a problem since
> > some changes of config spec are interactive (they require the
> > user to answer
> > yes or no) and so when invoked from Ant, they just hang,
> > since Ant can't
> > provide the response.  I have looked in the CC documentation
> > for a way of
> > forcing the command, but to no avail.  Any suggestions?
> >
> > Zak Saurin
> > _____________________________________________________________
> > Software Engineer
> > NetSys Technologies Ltd
> > a: Wellington House, 8 Upper St Martins Lane, London WC2H 9DL
> > t: +44 (0)20 7420 8418
> > f: +44 (0)20 7420 8401
> > e: zak.saurin@netsystechnologies.com
> >
> >  
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.295 / Virus Database: 159 - Release Date: 01/11/2001
> >
> >
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.295 / Virus Database: 159 - Release Date: 01/11/2001
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.295 / Virus Database: 159 - Release Date: 01/11/2001



--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message