Joseph, thank you for working on xalan. Would you please reply to the same thead to keep related messages together? Currently you send every update as a brand new message which makes it hard to follow.
--- Have you considered reviewing and merging https://github.com/apache/xalan-java/pull/9 so CI can prove that code builds on more than one machine? All these "Tried a build under windows" would much better be a CI running with different platforms and tests running with different Java versions. Have you considered creating a PR so everybody could see the suggested changes? Have you considered reviewing and merging the other open PRs? Have you considered inviting more committers? --- I maintain Apache JMeter, and it depends on Xalan. However, the more I follow the recent activity in Xalan, the more I reassure JMeter should stop using Xalan. There is some activity, however the team does not listen users, the team is not accepting contributions, and the development is literally halted. Who cares of a 3.0 function added on a 3.0 branch when the latest release on Central is broken and it breaks builds for everybody worldwide? That is a sign of non-maintenace to me. The main branch deletes all the code, and replaces it. It should not be like that. The goal of Apache Software Foundation is to produce **source** code, and such "delete all files, replace all files" commits make it hard to follow the **source** history and analyze issues. No maintenance && no development && no new committers == project is dead. Vladimir
