Cool. I remember that discussion now.
So what is the issue with requiring Xerces 2.0 and above? We have it in /turbine/jars, right? Or is it that we wanted to do it without requiring a specific parser, but got a Xerces 2.0 validator working first... -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers "Pete Kazmier" <pete@kazmier. To: Turbine Maven Developers List com> <[EMAIL PROTECTED]> cc: 06/05/02 01:09 Subject: Re: [PATCH] resubmit of 2 patches.. PM Please respond to "Turbine Maven Developers List" On Wed, Jun 05, 2002 at 11:52:42AM +1000, [EMAIL PROTECTED] wrote: > Martin, rather than catch the number format exception here, how about > we add the existing validate-pom target into the verify-project target > called before anything gets run, We purposely did not add the validate pom target into a target that is automatically run because the user is required to use Xerces-2.0 to get the validation working. At the time, we decided we didn't want to impose this requirement on the user. Instead, we opted to provide the target, and state in the documentation that Xerces-2.0 is required to use this target. -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
