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 ------- Additional Comments From [EMAIL PROTECTED] 2006-12-12 11:08 ------- (In reply to comment #1) > can you enter the exacts step to reproduce the bug, > the versions of the Perforce client and of the Perforce server which are involved. > Maybe if you can create a build.xml simulating the complete problem, including > creating the job (may be with an exec task), ... and attach it to this bug > report it can help. > Cheers, Antoine (In reply to comment #1) > can you enter the exacts step to reproduce the bug, > the versions of the Perforce client and of the Perforce server which are involved. > Maybe if you can create a build.xml simulating the complete problem, including > creating the job (may be with an exec task), ... and attach it to this bug > report it can help. > Cheers, Antoine The key point to reproduce is to create a user with a valid job specified in the JobView. 1) Create a Job: >p4 job testing1 2) create a JobView for the user - add the following line to the user spec at the bottom: >p4 user JobView: testing1 3) Then run the p4change task and print or try and use ${p4.change} and see that it has an extra 1 on the end. Server date: 2006/12/12 12:07:11 -0700 Mountain Standard Time Server version: P4D/NTX86/2005.2/93627 (2006/02/14) -- 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]
