# ant-dev mailing list archives

##### Site index · List index
Message view
Top
From "Anderson, Rob H - VSCM" <Anderson....@vectorscm.com>
Subject RE: enhanced pvcs task for PVCS version 7.5
Date Wed, 12 Mar 2003 17:47:13 GMT
Apparently there is some confusion around repository and config file. I
when you create a Version Manager project database a config file is created
in the archives directory. You can see the config file name and location
through the GUI if you right click the project database and choose
"Properties". You can, however, specify a config file to use when you create
the project database (in the advanced tab) or at any time through the
"Properties" dialog. For example: I have a local repository that I created
using the defualts ("Create a new config file" in the Advanced tab) for a
config file. The layout is as follows;

Project Database (-pr)
c:\pvcs
Config file
c:\pvcs\archives\cos0nbu1.cfg

I have a shared project database that was created with a custom config file
("Use an existing configuration file" in the Advanced tab)

Project Database (-pr)
s:\Projects\NOONAN
Config File
s:\configuration files\NOONAN.cfg

In both cases, using get works fine without the -c option unless I am doing
a get by promotion group. When doing a get by promotion group I will get an
error that says "get: Group "CM" does not exist in promotion hierarchy.",
because the promotion model is defined in the config file. So, if I specify
the config file with the -c option, this error goes away and the get by
promotion group works as expected.

So using the pvcs task is no different. Doing a normal "get" works fine, but
a "get by promotion group" fails with the error mentioned above. If there
was a configfile attribute to the pvcs task I could use it to get by
promotion group. Currently I can only use it to do a "get the default
revision". Does this make sense?

-Rob A

-----Original Message-----
From: cp533@daimlerchrysler.com [mailto:cp533@daimlerchrysler.com]
Sent: Tuesday, March 11, 2003 3:22 PM
To: Ant Developers List
Subject: RE: enhanced pvcs task for PVCS version 7.5

<Anderson>
PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default.
</Anderson>

"repository" attribute is used to point to config location, do you mean
some other configuration files; and as you know this a required attribute,
so no defaults.

<Anderson>
The advantage to using "pcli get" rather than
"get" is that pcli is smart about config files, which has been a problem
for
me with the existing PVCS task.I'm a little new to PVCS Version Manager, so
if there are other advantages please let me know. Of course pcli is pretty
slow compared to the old school "get".
</Anderson>

Following are advantages stated by our support team:-

All project teams that have been using the legacy Commands (i.e. get, put)
will need to convert to 'PCLI'. Using the PCLI commands is just like using
the I-NET client or Windows client. These three interfaces update
serialized database files that the PVCS Version Manager software uses.
These serialized database files contain all the information for the
archives.  So if one member is using PVCS I-NET and modifies an item that
modification will appear for another team member that is using the PCLI
commands.  Using the old sget or sput does not update these serialized
files.

1.) Easier/More User Friendly
2.) More Reliable
3.) Provides your team the choice to use Command Line or I-NET Client.
4.)May run a little slower since it is updating the serialized files.

<Anderson>
It would be nice if the existing PVCS task had a "configfile" parameter.
</Anderson>

problem when using with old get, with respect to the config files.

</source>

..(See attached file: Pvcs.java)
Chandra Periyaswamy

"Anderson, Rob  H

- VSCM"                  To:       "'Ant Developers
List'" <dev@ant.apache.org>
<Anderson.Rob@vec        cc:

torscm.com>              Subject:  RE: enhanced pvcs

03/11/2003 05:00

PM

"Ant Developers

List"

PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default. The advatantage to using "pcli get" rather
than
"get" is that pcli is smart about config files, which has been a problem
for
me with the existing PVCS task. I'm a little new to PVCS Version Manager,
so
if there are other advantages please let me know. Of course pcli is pretty
slow compared to the old school "get". It would be nice if the existing
PVCS
code. Please attach it to an email and send it to the list. Thanks,

-Rob A

-----Original Message-----
From: cp533@daimlerchrysler.com [mailto:cp533@daimlerchrysler.com]
Sent: Tuesday, March 11, 2003 12:14 PM
To: dev@ant.apache.org
Subject: enhanced pvcs task for PVCS version 7.5

Hi,

I'm a greenhorn to this list, so please pardon my mistakes if any.

I modified the pvcs task to work with PVCS VM version 7.5. Instead of a old
"get", I use "pcli get" in this modified version. It has been tested and
used in my project. I have tested on sun OS. I would be glad to submit the
source, if you'd like. Please let me know what you think.

I also think keeping the support for the old "get" may also seem important
for the community.

:o) Chandra Periyaswamy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org