dir="."
            executable="pcli"
            outputproperty="configFile1"
            vmlauncher="false"
        >
            
            
            
        
                    repository="${repository}"
            pvcsbin="C:PROGRA~1PVCSVMwin32in"
            force="yes"
            configFile="\${configFile1}"
            promotiongroup="${promotiongroup}"
        >
           
        
    


    
        

            
            
            
        
    

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:


href="http://marc.theaimsgroup.com/?l=ant-dev&m=99667939904467&w=2">http://marc.theaimsgroup.com/?l=ant-dev&m=996679

39904467&w=2

Zip file containing source code of proposed PVCS tasks:


href="http://marc.theaimsgroup.com/?l=ant-dev&m=99667939904467&q=p3">http://marc.theaimsgroup.com/?l=ant-dev&m=99667

939904467&q=p3

Subject: get: Group does not exist in promotion hierarchy.

Solution:

A promotion group on an archive exists only in conjunction with a configuration file. If you reference the config file containing the promotion model you'll find that you can perform a get -g.

Here are the various ways how to make VM find a configuration file:

1. Add option -c to your get command:

get -cc:pvcsabc.cfg -g

2. Create a vcs.cfg in the current working directory. If you already have a configuration file which has a promotion group defined, simply rename it to vcs.cfg and place it in the current directory.

3. Point to a configuration file in a VCSCFG environment variable.
Embed a configuration file by using the following command from your vmwin32inadmin directory:

vconfig -c ..vmwfvc.dll

You can find more information about this in the Command line reference guide, chapter 2 - Using Directives, Configuration Files - How VM Searches for Configuration Files'. The guide can be found in your PVCS directory under ooksvmRGVMCLIRG.PDF.

In my case, to get the Reports_Stage promotion group copy of EcfReport.java, this worked on the command line:

get -N -cY:ecfecf_adminmaster.cfg -gReports_Stage Y:ecfecf_project_dbarchivesReportsusinessobjectsEcfReport.javav

I downloaded the 1.5 alpha source, made some changes to Pcvs.java, recompiled, rejarred optional.jar, then ran some tests. It appears to work. If anyone wants a copy, let me know, and I'll send it along.

For that matter, is this something the Ant project would be interested in? I don't know how to submit it.

Thanks


PaulG


pfg@usinternet.com

for example in our shop a project named fooproj would have the follwoing direcotry structure:

fooproj/


fooproj/fooproj_project_db/

fooproj/fooproj_project_db/archives

fooproj/fooproj_project_db/archives/gui/

fooproj/fooproj_project_db/archives/gui/winmain.cpp



etc...



the best bet is to try the get command yourself and see what makes it work. then set the changes appropriately in your attributes