Answers Dave's easy one to head off potential confusion:
---- you [EMAIL PROTECTED] wrote ----
> quotes Shane:
> >-- I'd like to see a decent vote/comment period go by, and then unless
> >anyone complains, a backup...removal....
> >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
>
> I think we should retain anything that applies across all flavors of
> Xalan. Maybe some of the docs belong here? How about source files for
> the flavor-independent Web pages? I suppose that has implications for
> CVS, but is it really a problem or an opportunity?
> .................David Marston
Note that each of the directories I noted above are notably strictly
Xalan-J 1.x related, I'd like to note.
*All* Xalan-J 2.x code, documentation, builds, etc. is contained under
xml-xalan/java.
*All* Java and common testing code is contained under xml-xalan/test
To the best of my knowledge, *All* of the Xalan-C code, doc, builds, etc.
and some of the C-specific tests are contained under xml-xalan/c
Thus in the short term, let's not confuse the issues. Today's issue is
should we get rid of the 1.x project. Later on another, separate issue
about sharing other code, but I think that's a low priority since it'll be
a fairly small win compared to the maintenance it'll likely add. And when
that issue comes up, we can figure out then where to put that shared code.
-sc
- Shane
