Hi, Yes - it's because my tasks parse the forms that come back from the p4 client and the form handling stuff is in the P4Base baseclass. Most P4 commands either produce or require a text form to be filled in or modified - "p4 sync" is one of the few exceptions and I guess that's why <perforce> doesn't need any regexp handling, it only does a p4 sync (with various options).
I could have mucked about with Java's naff string handling but due to the textual interface to p4, it made sense to bite the bullet and use a decent Perl5 regexp library. Shame there's no Java API into perforce, even the C++ API seems to return 'forms' :-( and of course that'd mean .dll's and .so's and JNI - yuk! Hope this is OK, Les > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 14 November 2000 09:42 > To: [EMAIL PROTECTED] > Subject: Re: [Patch] New Perforce tasks > > > Les Hughes <[EMAIL PROTECTED]> wrote: > > > Les P.S. You'll need oro-2.0 to build them as well as the p4 command > > line client in your path - see build.xml for details. > > Does that mean, we'd be replacing an optional task that doesn't > require external libraries with a new one that does? I have no problem > to do so for those tasks that do things <perforce> can't do, but > I'm a little reluctant to replace the <perforce> task itself. > > Is ORO really a requirement for all of these tasks? > > Stefan >
