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=33260>. 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=33260 Summary: p4change task does not set p4.change property correctly Product: Ant Version: 1.6.1 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The p4change task does not set the p4.change property or the p4change task sets the p4.change property to the changelist number with a "1" appended. Problem occurs with some users but not others. Cause appears to be when the Perforce user in question has jobs associated with them through their jobview. If one job is associated, the p4.change property has the actual changelist with a "1" appended. If many jobs are associated with the user, p4.change is not set. Note that the native Perforce command "p4 change -o" (which is used by the p4change task) reports all jobs associated with a user. I'm guessing that when jobs are associated and are reported by this command, the resulting text is "unexpected" and not handled correctly by the code implementing the p4change 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]
