O.K. now we've got two blue bubbles again both on jdk 1.6 as well as jdk 1.7 "no-test" profiles:
https://builds.apache.org/job/Camel.trunk.notest/1860/ https://builds.apache.org/job/Camel.trunk.notest.jdk7/2/ Indeed the buggy annotation processing by JDK 1.6 was the root cause of the problem we were facing. For this to work properly I restricted the new automated HTML document generation to JDK 1.7+ as: - Even using the currently latest ORACLE JDK 1.6 (build 45) it does not generate the HTML documentation anyway - It causes build problems on the CI-Server So IMHO the release manager of the upcoming 2.12.0 release should use JDK 1.7 instead of JDK 1.6 for the build through which we would have a proper HTML documentation inside the generated camel-core-2.12.0.jar etc. On the other hand as we instruct the maven-compiler-plugin to consider our code base as source=1.6 & target=1.6 then everything should be O.K. with the generated class files for folks still using JDK 1.6. BTW we have had already a similar thread regarding this: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-0-take-2-tp5730599p5730636.html Makes sense? Babak -- View this message in context: http://camel.465427.n5.nabble.com/Our-builds-looks-really-bad-tp5731673p5731743.html Sent from the Camel Development mailing list archive at Nabble.com.
