We need to pick up the saxon 18.104.22.168 with some bug fixing and enhancements.
Applied patch into trunk
Willem, in which maven repo is saxon9he located?
The CI servers may not be able to find it, from a clean build with no m2 cache.
The maven repo is here
Ah great. There seems to be some examples or whatnot that will fail missing this dep
See console output from
I guess adding that sxm repo will fix that.
But then I don't get it why the newest build  of today morning with full test did pass concerning this dependency!
You should try deleting/moving your local m2 repo
So maven will have to download all the JARs again. Then you may see if any JARs is missing
That's already clear to me
My concern is the CI-Server itself. I assume the Jenkins builds for all of the Apache projects on the CI-Server use the same m2 cache (maybe somewhere along the path /home/jenkins/.m2/repository). Now:
And now what I don't get is that if the fulltest run could successfully resolve the saxon9he dependency, how is it possible that the notest run 2.5 hours later could not resolve that anymore, as at that time the saxon9he should have been already available inside the m2 cache of the user "jenkins"!
There are lots of CI-Servers running in the Apache build fram. I don't think they are sharing the same m2 cache. It will cause lots of problem when different build try to install the same artifacts at the same time.
The whole INFRA Jenkins/Maven setup is somehow not much clear to me and we have currently also really wired behaviour on the Window builds as well  about which nobody from INFRA could resolve the problem til now.
What also seems to be really odd to me is that why INFRA makes use of a SNAPSHOT version (1.447-SNAPSHOT) of Jenkins!
The Saxon bundle version in the features.xml is no longer valid. It refers to a SNAPSHOT which has already been released. Kindly apply the attached patch.
Patch was applied by Christian.