[xslt20][discuss] JDK 1.1.x support in the future Xalan

[Shane Curcuru]

Please note: I'm discussing *only* the xslt20 branch here: the prototype 
we're implementing future XSLT specs on, that might become Xalan 3.x 
someday (version number 3 is made up, but it sure sounds good...).

I propose that we explicitly drop JDK 1.1.x support for the xslt20 
branch.  Given the long timeframe of a finished 3.x release and the myriad 
times that we will want to use Collections classes, new classloader 
features, or various optimizations that don't work in 1.1.x, I think we 
need to just say now that we're dropping 1.1.x support for both compilation 
and runtime.

I know that this has an impact both on some legacy environments as well as 
many browsers, but I'm not sure that we can efficiently build a 
high-performing Xalan 3.x release otherwise.  Plus the fact that we rely on 
Xerces, JAXP, SAX and DOM, each of which may well drop 1.1.x support by then.

Comments, questions, concerns?
Remember - this would not affect the current 2.x releases, only future 
releases from the xslt20 branch.

- Shane