Return-Path: Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Delivered-To: mailing list dev@ant.apache.org Received: (qmail 87583 invoked from network); 12 Mar 2003 19:43:06 -0000 Received: from fxshpr08.extra.daimlerchrysler.com (HELO fxshpr06.extra.daimlerchrysler.com) (129.9.80.165) by daedalus.apache.org with SMTP; 12 Mar 2003 19:43:06 -0000 Received: (from uucp@localhost) by fxshpr06.extra.daimlerchrysler.com (8.12.8/8.9.0) id h2CJfD8D029780 for ; Wed, 12 Mar 2003 14:41:13 -0500 (EST) Received: from nodnsquery(129.9.147.104) by fxshpr08.extra.daimlerchrysler.com via csmap (V6.0) id srcAAA9hayi6; Wed, 12 Mar 03 14:41:13 -0500 Received: from odmrspr2-hme0.oddc.chrysler.com ([53.231.2.113]) by shconpr2-hme0.shdc.chrysler.com (Mail-Gear 2.0.0 bld 58) with SMTP id M2003031214430515638 for ; Wed, 12 Mar 2003 14:43:05 -0500 Received: from sodddg03.wk.dcx.com (odebup07-hme0.notes.chrysler.com [53.231.71.77]) by odmrspr2-hme0.oddc.chrysler.com (8.12.8/8.11.2/daimlerchrysler-relay-1.1-kcd) with ESMTP id h2CJh4Y5028537 for ; Wed, 12 Mar 2003 14:43:05 -0500 (EST) Subject: RE: enhanced pvcs task for PVCS version 7.5 To: "Ant Developers List" X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: cp533@daimlerchrysler.com Date: Wed, 12 Mar 2003 14:37:15 -0500 X-MIMETrack: Serialize by Router on sodddg03.wk.dcx.com/Server/Prod/DCX(Release 5.0.11 |July 24, 2002) at 03/12/2003 02:33:02 PM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks! I think, I get it now. Most of the time, I work with the support team to sort any issues, I wa= s not aware (that's what the support team wants) of the inside details. I= just have looked at the docs for old(just to differentiate from pcli) = pvcs commands, that goes like this for configuration files.... Version Manager has a prescribed order in which it searches for configuration files. Version Manager first reads the configuration file that is embedded in the VCONFIG files (this is usually the master configuration file). The most direct way to specify a configuration file is to use a command's -c option. If you don't specify a configuration file using this option, Version Manager checks for a default configuration file (named vcs.cfg) in the current directory. If this file does not exist, Version Manager checks for the VCSCFG environment variable, which specifies the name and location of the configuration file to use. I happen to have the VCSCFG set in my profile, that is why I did not ha= ve problem with old get, even when I use with promotion group. Hope this helps... Chandra Periyaswamy MPI - Incentives tie-line: 754-5328 email: cp533@daimlerchrysler.com = =20 "Anderson, Rob H = =20 - VSCM" To: "'Ant Develope= rs List'" =20 Subject: RE: enhanced p= vcs task for PVCS version 7.5 =20 = =20 03/12/2003 12:47 = =20 PM = =20 Please respond to = =20 "Ant Developers = =20 List" = =20 = =20 = =20 Apparently there is some confusion around repository and config file. I= apologize for not being very clear about this. Let me explain. By defau= lt, when you create a Version Manager project database a config file is cre= ated in the archives directory. You can see the config file name and locatio= n 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 crea= ted 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 d= oing a get by promotion group. When doing a get by promotion group I will ge= t 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 spe= cify 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 the= re 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 PVCS task works with version 7.5 as is, unless you are pointing to a co= nfig file other than the default. "repository" attribute is used to point to config location, do you mean= some other configuration files; and as you know this a required attribu= te, so no defaults. The advantage to using "pcli get" rather than "get" is that pcli is smart about config files, which has been a proble= m 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 pre= tty slow compared to the old school "get". Following are advantages stated by our support team:- All project teams that have been using the legacy Commands (i.e. get, p= ut) will need to convert to 'PCLI'. Using the PCLI commands is just like us= ing 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 th= at 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. It would be nice if the existing PVCS task had a "configfile" parameter=