Return-Path: Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@xml.apache.org Received: (qmail 36955 invoked from network); 10 Oct 2001 21:41:43 -0000 Received: from lotus2.lotus.com (129.42.241.42) by daedalus.apache.org with SMTP; 10 Oct 2001 21:41:43 -0000 Received: from internet2.lotus.com (internet2 [172.16.131.236]) by lotus2.lotus.com (8.11.4/8.11.4) with ESMTP id f9ALgTe20020; Wed, 10 Oct 2001 17:42:29 -0400 (EDT) Received: from cammail01a.lotus.com (f3n5pd.lotus.com [9.95.6.250]) by internet2.lotus.com (8.11.4/8.11.2) with ESMTP id f9ALfJw26829; Wed, 10 Oct 2001 17:41:19 -0400 (EDT) Subject: Commons copies of DOM/JAXP/SAX checked into Xalan To: commons-dev@xml.apache.org, xalan-dev@xml.apache.org Cc: Edwin.Goei@eng.sun.com, cmanolache@yahoo.com X-Mailer: Lotus Notes Release 5.07a May 14, 2001 Message-ID: From: Shane_Curcuru@lotus.com Date: Wed, 10 Oct 2001 17:35:56 -0400 X-MIMETrack: Serialize by Router on CAMMAIL01a/CAM/M/Lotus(Release 5.0.8 |June 18, 2001) at 10/10/2001 05:41:18 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N For those who pay attention to this stuff: I've bulk-checkedin the copies of DOM, SAX, and JAXP standards files from the xml-commons repository into the xml-xalan repository. While the long term plan is to always pull these standards-based files from the xml-commons repository, we haven't quite taken that step. Also, while the current build script attempts to use the files in xml-commons directly when compiling, it didn't use them for building javadoc, and some of that was outdated. Tomorrow I'll diff these with the previous xalan copies (which I tagged 'before-commons') to make sure there weren't any bugfixes that we had applied to our copies but that didn't make it into the commons area. Also note, these files aren't technically under our control - they each are files that are defined by external standards groups. So if we want to make fixes to them (I'm thinking of Bugzilla#2291 especially here) then we really need to also take these issues up with the external standards groups that define them. - Shane