The Apache Jenkins build system has built Camel.trunk.notest (build #1910)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1910/
to view the results.
This first run didn't went well. The artifacts were not uploaded to Nexus
and the tagged Camel 2.10.5 release had the version number
2.10.5-SNAPSHOT...
Next try later today...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
The problem (reported in the jira) is that by using this option the logic
is wrong so that the schema is not read correctly - regardless if
true|false and JDK it's running on - e.g. not tied to buggy JDK - but bug
in the validator code, which the test i submitted shows.
2013/6/21 Claus Ibsen
>
Hi
Can you explain why you did this code change?
It seems wrong to me to change the code to force using a byte[] where
the existing code works fine, and is optimized for streams. And don't
load the data into a 2nd byte[] which mean 2x the memory comsumption.
Also the option useSharedSchema=false
