Tuesday, January 22, 2002 03:05 PM
Andrew May has written replacements for the pvcs task which accept a configFile attribute where appropriate. (See
links below.) Unfortunately, his pvcsget task doesn't support automatic discovery of config files. Here's a
parameterized target which uses pvcs's command line interface (pcli) to find the config file, and a call thereto:
Due to the exec task, this target is Windows-centric. Hopefully, pcli will be easier to deal with in a Unix
environment. Sorry I can't test that since we don't have a Unix installation of PVCS yet.
With this approach, you can operate on only one project at a time, but at least that's more than zero. Of course,
if you're willing to forego parameterization and put up with the exec ugliness before every pvcsget, then you can
include as many pvcsproject elements as you like.
Introduction to proposed PVCS tasks by Andrew May:
Zip file containing source code of proposed PVCS tasks: