On Mon, Nov 08, 2021 at 07:07:15PM -0500, Bridger Dyson-Smith scripsit:
There's almost certainly a much nicer way to do this - eg the examples you've provided - but could another option be to build out a `proc:execute()` call? It wouldn't be nearly as elegant, and may cause additional processing in the output, but that way you would have full access to command line Saxon options and switches.
I had no idea proc:execute() was even there. I'd been looking for a BXS equivalent. (Step one; read all the docs. Step two; somehow retain all the docs.)
Best, (and apologies for the water cooler suggestion!)
An entirely helpful suggestion!
If I can get the transform step to behave, I am pretty sure I can manage the whole multi-step build-and-test process from a hierarchy of BXS calls with common configuration and that makes me happy. (Or at least much happier than the alternatives!)
Much appreciated!