Maven is rather common today, and one of its best features is the ability to automatically download and use the latest bug fix of a dependency. Hence, one can rely to only get the latest bug fixes, but no (possible incompatible) API changes, when following some simple common rules.
The most important rule is void by SAXON. It is that the version schema must be:
This is essential to allow Maven to detect "later" versions (hence, deal with the parts and four single integers but not as one large string).
Unfortunately SAXON is using the following schema:
...hence Maven cannot detect that 22.214.171.124 is actually the second build of 9.4.0, and fails to automatically download any bug fixes of 9.4 when instructed to do so using the range [9.4, 9.5). :-(
It would be really great if you could commit to the "right" schema when uploading versions into Maven Central. That means, you can leave all as it is, but just have to provide the dashed version number (instead of the dotted) in the POM. :-)