Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@xml.apache.org
Message-ID: <3BDCB02D.30E77B9C@gmx.de>
Date: Mon, 29 Oct 2001 02:26:09 +0100
From: Martin Stricker <shugal@gmx.de>
Organization: http://martin-stricker.de/ http://www.surfo.net/
 http://www.masterportal24.com/cgi-bin/YaBB.cgi
MIME-Version: 1.0
To: general@xml.apache.org
Subject: Re: [PROPOSAL-strawman] xml-commons source usage in other projects
References: <OF9E6E245B.9DA7FF70-ON85256AEF.006F8F82@lotus.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Shane_Curcuru@lotus.com wrote:
> 
> Steps to do this might be like (for each project):
> - Remove all DOM/SAX/JAXP code from the project's CVS tree
> - Checkin a current copy of the xml-commons DOM/SAX/JAXP code into
> /project-name/src/external/* directories (yes, this is kind of moving
> sources in your repository)
> - Modify your build.xml to have a 'copy-commons-src' target between
> your init/prepare and compile targets, that works something like:
> 
> - Checks a ${use-commons-src} flag that developers or projects can
> default to force useage of commons copies or local copies of files.
> (This is for projects that want to explicitly work one way or the
> other by default)
> 
> - Checks if an xml-commons/java/external/build.xml file exists: if so,
> copy the xml-commons copies to project-name/src directory
> - If not, and there's a local src/external directory, then copies it
> project-name/src directory
> - If the local src/external copy isn't there, then do nothing
> Note that each of the copies should use the Ant uptodate functionality
> to avoid copying unchanged files; xalan doesn't do this yet.
> 
> - your compile target works as normal, compiling stuff from /src into
> your build area and .jars
> 
> - your distro target then copies the /src tree into the distro,
> excluding the src/external directory.
> 
> This way, developers who work from checked out copies of xml-blah
> repositories can choose to also checkout the always-up-to-date
> xml-commons tree as well if they want.  If they don't, they can still
> work normally although they might be using the (potentially) older
> copies in their local src/external directory.

Ummm, maybe I'm just too stupid, but why should all the projects keep a
copy of their xml-commons code if it already is in xml-commons? Please
enlighten me since I get the feeling that this approach obsoletes
xml-commons.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org