(There may still be some tweaking there to make sure all the fields people want to see in the POM are being filled in correctly by the Maven build. Need to find cycles to review those tasks.)
If release has happened, it must be possible....2) I've posted a Jira work item for my suggestion that, if the XSLT3 prototype logic can cleanly be turned into Xalan Extensions, it could be released as part of the Xalan Extension Library and thus start shipping with base Xalan. Some of the EXSLT library was, in fact, early prototypes of functions that XSLT3 would later provide, and provides some illustration of how Xalan functions are written (and how we've handled them in test). Downside is that it would require the new functionality be accessed with namespace prefixes; upside is that it would make the division between portable 2.0 and half-portable 3.x-subset much clearer, and would emphasize keeping changes to core Xalan clean and isolated to minimize risk of regression in 2.0 compatibility.
I've assigned it to Mukul, but others may want to weigh in on what priority this should be given and/or whether it's worth doing at all.
3) My time is still going to be erratically available for the next 4 weeks at least, due to a series of personal commitments. But I do want to get Xalan back onto an actual release cycle, and make enough progress whittling down the backlog to justify regular releases.
-- ` /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. Feel free to call him on it.
OpenPGP_0xFFBAFF963D937815.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
