DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14395

No way to set additional global options for Perforce tasks





------- Additional Comments From [EMAIL PROTECTED]  2003-01-29 10:02 -------
I have tested this fix and it works OK for me.
The way to describe the fix is the following :
a new 
attribute "globalopts" can be added to all Perforce tasks.
You can put in it all the strings 
described by p4 help usage.
Note that the Perforce client, user and port parameters are already 
covered by the properties p4.client, p4.user and p4.port
This attribute can be used to enter 
the password for instance :
Here a snippet :
<?xml version="1.0"?>
<project 
name="testperforce" default="testperforce" basedir="C:\dev\gnu">
    <property 
name="p4.client" value="levyant_dev_ant"/>
    <property name="p4.port" 
value="localhost:1666"/>
    <target name="testperforce">
      <echo>
      trying p4fstat with 
correct password
      </echo>
        <p4fstat showfilter="all" globalopts="-Pbertrand">
            
<fileset dir="depot" includes="**/*"/>
        </p4fstat>      
      <echo>
      trying p4fstat with wrong 
password
      </echo>
        <p4fstat showfilter="all" globalopts="-Pfoobar">
            <fileset 
dir="depot" includes="**/*"/>
        </p4fstat>      
    </target>
</project>
here the output of 
the snippet :
testperforce:
     [echo]
     [echo]       trying p4fstat with correct password
     
[echo]
  [p4fstat] Following files exist in perforce
  [p4fstat] C:\dev\gnu\depot\foobar
  
[p4fstat] C:\dev\gnu\depot\hello
  [p4fstat] Following files do not exist in perforce
     
[echo]
     [echo]       trying p4fstat with wrong password
     [echo]
  [p4fstat] Following files exist 
in perforce
  [p4fstat] Following files do not exist in perforce

BUILD SUCCESSFUL
Total 
time: 1 second
Note that the wrong password does not cause a build exception, it probably 
should, but this is another issue.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to