Xerces is optional because we should be able to run with other DOM/SAX input and output.
I suspect the serializer is required because some of the Recommendation's requirements must be implemented there, but I'm not 110% certain. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: Eric J. Schwarzenbach <eric.schwarzenb...@wrycan.com> Sent: Thursday, April 13, 2023 11:47:32 AM To: j-users@xalan.apache.org <j-users@xalan.apache.org> Subject: Re: [VOTE][RESULT] Release Apache XalanJ 2.7.3 based on RC10 I'm happy to help in any way, but I assume it requires someone with a login to that apache repository manager to upload the files to it. In case this helps, here is a copy of the pom for the last version of xalan.jar from maven central, edited to update: the xalan version to 2.7.3 the xercesImpl dependency to 2.12.2 the xalan serializer dependency to 2.7.3 the apache parent project version to the latest, which is 29 (the last version of this pom used 4. I'm just guessing this should be set to 29, the latest appearing in maven central. I don't really know the significance of this parent reference). The URL to https://xalan.apache.org/xalan-j/ (the last version had https://xml.apache.org/xalan-j/ which has "Xalan-Java Version 2.7.1" at the top. Why does this page still exist?) Note that the xercesImpl dependency is marked as optional, and the xalan serializer dependency is not. Is this correct? Any other changes needed? The serializer dependency means that a serializer jar and pom must be uploaded first I think. If this is helpful I can post an updated pom for that too. On 4/13/23 02:04, Vladimir Sitnikov wrote: I've filed https://issues.apache.org/jira/browse/XALANJ-2644 to track publishing Xalan to Central. Could anybody upload the release files to repository.apache.org<http://repository.apache.org> pease? Vladimir -- Vladimir
