Re: Generic VCS module test specification

Hi Kenneth,

see my comments below ...

kenneth.w.vanbooven@mail.sprint.com wrote:

>Hi Jirka

>

>After reading your e-mail I realized the command is working as intended. I was hoping it would change the read-only attribute of the file as the check-out option in PVCS does but since it wasn't designed to, it is working correctly.

>

Great, I was afraid we had new bug ! :-)

>Since there are no Check-out or Check-in options I could make my own. To do this I would copy the lock and unlock commands, rename them Check-out and Check-in and edit the commands to change the attribute of the file in "Commands Executed After Success". Would this be the correct method to handle this?

>

Excuse my ignorance but I didn't understand exactly what you want to

achieve. You woud like to have special checkbox "Make the file writable"

in the dialog of "Lock" command ? If so, follow this procedure:

1. Change the "Input Descriptor" property of "Lock" command a little

bit. Insert ASK_FOR(WRITABLE,"Make the file writable.", false) string

between LABEL(...) and SELECT_RADIO_EXPERT(...) sections.

2. Modify the "Exec" property of the same command a bit. Insert &&

attrib $[? WRITABLE][-r][+r] \"${WORKDIR}${PS}${FILE}\" string before

${NUR} string.

3. If you then invoke "PVCS | Lock" on a file, you will have an option

to choose what you like.

Let me know about how it works. My solution is for Windows. For Unix

replace 'attrib' with 'chmod', '-r' with 'u+w' and '+r' with 'u-w'.

Hope that helps.

Regards Jirka

>

>

>Thanks for all your help

>

>Kenneth Van Booven

>System Integrator IV

>10750 El Monte

>Overland Park, KS 66211

>(913)-624-8083

>

> --Original Message--

>From: jiri.kovalsky [mailto:jiri.kovalsky@sun.com]

>Sent: Tuesday, July 16, 2002 5:25 AM

>To: jiri.kovalsky; kenneth.w.vanbooven; nbusers

>Subject: Re: Generic VCS module test specification

>

>Hi Kenneth,

>"PVCS|Lock" command does not influence read-only attribute of files. It

>only locks given file for you in PVCS archive. However, the bug would be

>if the status of your file wouldn't change from [Current] to [Current;

>1.?] (your_name). Does this works for you correctly ? In which test case

>does it fail ? "4.12 Lock a file" ?

>

>Here is an execution string of my Lock command:

>cmd /X /C " vcs -y -l

>\"D:\Tests\PVCS\Repo1\archives\A_File.java-arc\"(\"D:\Tests\PVCS\Work1\A_Fi le.java\")

>"

>and its "Standard Output":

>Locked "D:\Tests\PVCS\Repo1\archives\A_File.java-arc" rev 1.1.

>

>To compare them, switch to "Runtime" tab of explorer, expand "VCS

>Commands" and your PVCS filesystem nodes and double click "Lock" node.

>If you want to modify the command, invoke "Customize" on your PVCS

>filesystem, switch to "Advanced" tab and push "Edit Commands...". Expand

>"PVCS" node and select the first "Lock" node. You can adjust "Exec"

>property in the property sheet.

>

>Hope that helps.

>Regards Jirka

>

>P.S. I am forwarding this answer also to nbusers@netbeans.org so that

>others can take advantage of this advice.

>

Kovalsky,Jiri at 2007-7-2 23:26:10 >