Hi Matt, Feel free to change the code and submit a patch. Using the default change from Ant isn't something I've ever really needed to do so I haven't yet got round to coding it ;-) In fact, I'm not actually using Perforce on my current project - it's a VAJ repository & ClearCase shop so it will be a while before I get back to enhancing the P4 tasks.
The text change you mention is pretty straight forward - modify P4Submit and then just implement a new P4OutputHandler and use oro to do the substitution for you (there's a Perl5Util object in P4Base called util that'll help with this). In fact (from memory) I think P4Submit does something like this anyway. Hope this helps Bye, Les PS Could you keep mails to the dev list? That way they get into the archive and someone else may offer to help out as well. > -----Original Message----- > From: Matt Bishop [mailto:[EMAIL PROTECTED] > Sent: 26 June 2002 19:21 > To: [EMAIL PROTECTED] > Subject: Ant 1.5's PSubmit class > > > I'm looking at the P4Submit class and found it doesn't > support the default changelist. Are you still working on > these tasks? If not, can you tell me who is? > > I need to add this in ASAP and am thinking of storing the > content of the change description as a Text object in the tag: > > <p4submit> > Fixed bug#244543 > Added new feature to change everything to yellow. > Smoke test:pass > </p4submit> > > The text object would replace the <enter description here> > string in the changelist report. > > ____________________________________________ > > Matt Bishop > bea Systems > 999 N. Northlake Way > Seattle, WA 98103 > > 206.926.2924 - phone > 206.675.8250 - fax > > http://www.bea.com > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
