> We cannot bundle Saxon in the binary package because there are classes in > the Saxon jar that haven’t been approved as Apache-compatible. While > other Apache projects “use” Saxon, the first four I looked at don’t appear > to bundle it in their binary packages. At least, I don’t see saxon*.jar > in the binary packages or mention of Saxon in the LICENSE and NOTICE files > of those packages.
So, the others get to use Saxon without any mention of it in their legal docs, and we have to remove it or at least bother the user about downloading it? At least we got rid of those other ones; two steps forward, one step back, I guess ;-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
