[
https://issues.apache.org/jira/browse/CAMEL-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189754#comment-13189754
]
Babak Vahdat commented on CAMEL-4910:
-------------------------------------
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:
- The newest fulltest run was at Jan 20, 2012 6:01:25 AM:
https://builds.apache.org/job/Camel.trunk.fulltest/665/
- The newest notest run was at Jan 20, 2012 8:29:25 AM:
https://builds.apache.org/job/Camel.trunk.notest/1442/
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"!
> Upgrade saxon version to 9.3.0.11
> ---------------------------------
>
> Key: CAMEL-4910
> URL: https://issues.apache.org/jira/browse/CAMEL-4910
> Project: Camel
> Issue Type: Task
> Components: camel-saxon
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.10.0
>
>
> We need to pick up the saxon 9.3.0.11 with some bug fixing and enhancements.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
