Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 70047 invoked from network); 3 Apr 2000 11:56:10 -0000 Received: from e24.nc.us.ibm.com (32.97.136.230) by locus.apache.org with SMTP; 3 Apr 2000 11:56:10 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e24.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id HAA28816 for ; Mon, 3 Apr 2000 07:44:05 -0500 From: rubys@us.ibm.com Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [9.67.228.36]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v2.07) with SMTP id HAA31480 for ; Mon, 3 Apr 2000 07:56:09 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852568B6.00419006 ; Mon, 3 Apr 2000 07:56:07 -0400 X-Lotus-FromDomain: IBMUS To: ant-dev@jakarta.apache.org Message-ID: <852568B6.00418E4A.00@d54mta04.raleigh.ibm.com> Date: Mon, 3 Apr 2000 07:48:29 -0400 Subject: Re: I want to become an Ant developer Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Stefan Bodewig wrote: >It took me a rather long time to see that the parser shipped with Ant >chokes on comments inside elements like > > >/> > >nsgmls didn't complain at all and I'm not sure who is right here, but >the provided parser exception sure didn't help at all. I agree - the current Ant plus the current parser doesn't tend to produce very helpful error messages. You can change to Xerces by modifying org/apache/tools/ant/parser.properties. Hopefully shortly (I imagine this month), the xml parser will be removed from Ant and whichever parser you happen to have in your classpath will be the one used. - Sam Ruby