DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25711>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25711 Perforce task 'p4submit' should *not* set p4.needsresolve to 0 upon success [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Target Milestone|--- |1.6.1 ------- Additional Comments From [EMAIL PROTECTED] 2003-12-23 15:01 ------- Eric, you are right, there is a problem here. I wrote this task :-( and I followed the bad example of other Perforce tasks which call Project.setProperty(). The real solution - conform to the ant philosophy about properties - would be to add an attribute p4needsresolveproperty where the user would give a name to a property which would be set if the submit needs resolve. Will try to add this new attribute for ant 1.6.1. Cheers, Antoine --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]