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=29396>. 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=29396 Allow P4Change to edit changelists as well Summary: Allow P4Change to edit changelists as well Product: Ant Version: 1.6.1 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Perforce server may rename changelists upon submission, which in our environments occurs often. In case the change number as obtained by ${p4.change} is used for versioning purposes (as we do) in the MANIFEST.MF of jar files generated during the automated build process there is the chance there is no direct relation between the build number and the final change number under which the nightly has been submitted. In case p4change would allow us to edit a created but still not submitted changelist then we could at least put the original changelist number in the description. That way we can always track the final changelist number back to the build number. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
