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=42824>.
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=42824

           Summary: p4labelsync cannot use revision paths with timestamps
           Product: Ant
           Version: 1.7.0
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Optional SCM tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: [EMAIL PROTECTED]


The p4labelsync task implementation will not work with depot paths that use
timestamps.  This prevents users from synch'ing labels at specific times in the
revision history.

e.g.
//depot/my/path/...@"2007/07/05:16:50:00"

(the "2007/07/05:16:50:00" above follows Perforce's convention for specifying
specific timestamps)

This is because p4labelsync uses the colon character (:) is used as a separator
for multiple paths.  It should only use the semi-colon (;) for this.  

The result is that the path will be garbled with newlines (as shown in the
resulting verbose output):

[p4labelsync] P4Labelsync exec:
[p4labelsync] Executing 'p4' with arguments:
[p4labelsync] '-phost:1666'
[p4labelsync] '-umyuser
[p4labelsync] '-cmyworkspace'
[p4labelsync] '-s'
[p4labelsync] 'labelsync'
[p4labelsync] '-l'
[p4labelsync] 'MY_LABEL'
[p4labelsync] '//depot/my/path/[EMAIL PROTECTED]/07/05 
[p4labelsync] 16  <-- incorrect!!
[p4labelsync] 50  <-- 
[p4labelsync] 00' <--

Please remove the ':' as a separator or provide an alternative method to specify
timestamps when using this particular task.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to