Here's Shane's
-0
vote for this (Scott's proposal to remove all Xalan-J 1.x source). Only
giving people on the mailing list one day to review a major change like
this is waaaay to short a vote period. Heck, I don't even check xalan-dev
every single day myself.
Other topics:
-- Do any users really want to see more Xalan-J 1.x builds? If so, are
some of our users therefore volunteering to actually do the work here? If
not, great, let's have a party and declare 1.x dead.
-- Other projects also put a lot of stuff into one CVS tree. Xerces has
/java, /c, /perl, and a variety of tests embedded under xml-xerces CVS
tree. One admitted difficulty with xml-xalan is that the 1.x code was
rooted at the top level, which makes it hard to separate from other bits of
xalan.
-- I'd like to see a decent vote/comment period go by, and then unless
anyone complains, a backup of the full Xalan-J 1.x CVS repository (not just
the files, but the whole repository) made, and then (with aid of a CVS
expert) actual filesystem removal of all files relating to Xalan-J 1.x
(i.e. not just CVS putting them in the attic, but actually deleting the
repository files). Note that this includes each of the following areas in
/home/cvs/xml-xalan:
xml-xalan/* files (we should re-commit a README here that points
users to each individual subproject and to the tests)
xml-xalan/bin
xml-xalan/docs
xml-xalan/samples
xml-xalan/src
xml-xalan/xdocs
-- At that point, I would think users could then easily do separate CVS
checkouts of 'xml-xalan/java', 'xml-xalan/test' and 'xml-xalan/c' easily.
If there's a serious performance problem and someone can volunteer time to
fix it, then we can talk about moving other repositories around.
-- In a few weeks I'd like to update and improve the 'smoketest' target and
related stuff to be more robust and include more tests. However I plan to
keep all the testing logic in the xml-xalan/test repository, so to run the
smoketest you will still need the testing tree, since we don't have the
resources to manage separate testing trees.
- Shane
---- you [EMAIL PROTECTED] wrote ----
> OK, then let me take this oppurtunity...
>
> On Tuesday I would like to go ahead and remove all files in xml-xalan/src
> (i.e. XalanJ 1).
>
> In order to stop this I will need a -1 from one of the committers, or
> strong disagreement from one of the users.
>
> The files will still be in the CVS attic, of course, and most of the old
> builds are still in http://xml.apache.org/dist/xalan-j/old/.
>
> Note that we have also deprecated the XalanJ1 compatibility APIs for
> XalanJ2, and plan to remove these also in a release or two.
>
> -scott
