DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31654>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31654 Perforce Version Control Task will only work with default client spec. Summary: Perforce Version Control Task will only work with default client spec. Product: Ant Version: 1.6.1 Platform: PC OS/Version: Other Status: UNCONFIRMED Severity: Major Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Perforce version control system lets users interface with its repository using a client specification, or "client spec". Each client spec is configurable for a project, and is useful in separating out change lists, file checkout locations, etc for different projects a user may be working on. Ant ships with a P4 Task that allows users to build ant projects that can interact with their Perforce server. Each P4 task has the following properties: 1) port - P4PORT The p4d server and port to connect to 2) client - P4CLIENT The p4 client spec to use 3) user - P4USER The p4 username 4) view - The client, branch or label view to operate upon. Item 2 (the Client property) appears to be ingored by the Task. In all my projects, this value always defaults to the default Client for my Perforce instance. I have debugged this and seen that I am passing the correct Client name in to the Task's Client attribute, but it is always ignored in favor of the default Client. To get my P4 Tasks to work I have to change the default Client in Perforce to be the one I want to operate on. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
