<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:-
<adv>
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.
</adv>
<Anderson>
It would be nice if the existing PVCS task had a "configfile" parameter.
</Anderson>
Can you explain a bit more about this? because I don't seem to have any
problem when using with old get, with respect to the config files.
<source>Please find the attachment. Don't miss the added (two) properties.
</source>
..(See attached file: Pvcs.java)
Chandra Periyaswamy
"Anderson, Rob H
- VSCM" To: "'Ant Developers
List'" <[EMAIL PROTECTED]>
<[EMAIL PROTECTED] cc:
torscm.com> Subject: RE: enhanced pvcs task
for PVCS version 7.5
03/11/2003 05:00
PM
Please respond to
"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
task had a "configfile" parameter. I would like to check out your source
code. Please attach it to an email and send it to the list. Thanks,
-Rob A
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 12:14 PM
To: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
