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 46971 invoked from network); 7 Jul 2000 01:33:40 -0000 Received: from e21.nc.us.ibm.com (32.97.136.227) by locus.apache.org with SMTP; 7 Jul 2000 01:33:40 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id VAA30154 for ; Thu, 6 Jul 2000 21:23:23 -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 v4.9) with SMTP id VAA58376 for ; Thu, 6 Jul 2000 21:33:40 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 85256915.0008901B ; Thu, 6 Jul 2000 21:33:31 -0400 X-Lotus-FromDomain: IBMUS To: ant-dev@jakarta.apache.org Message-ID: <85256915.00088E72.00@d54mta04.raleigh.ibm.com> Date: Thu, 6 Jul 2000 21:33:00 -0400 Subject: RE: JAXP (was: Urgent help with Javac task) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Jose Alberto wrote: > Finally, does any one know the reason why ant's binaries do not ship with > its own copies of JAXP binaries in its lib directory? I see no reason why > we need to go to javasoft and download JAXP and pollute our classpath. > Notice that we do not need to pollute it for ANT, but just for JAXP. Is > there any issue on shipping binaries for JAXP? There are no licensing issues, and I will add them to tonight's binaries. Those that prefer Xerces can simply replace the jars. - Sam Ruby