Hi All, I introduced a failure on builds.apache.org today; the odd thing was that the failing test ran perfectly fine on my local environment and on other developer’s environments. It was a failure in a mock library and I determined it was caused by a JDK version difference. I use JDK 1.6 and builds.apache.org uses JDK 1.7
This raises an important question: If Ambari supports JDK 1.6, we should be building with JDK 1.6 in order to catch compilation issues? I could easily introduce a JDK 1.7 method or class and builds.apache.org won’t catch it. I’m going to work on fixing my unit test now that I can see it failing after switching to JDK 1.7, but I think we need to change builds.apache.org to JDK 1.6. Community thoughts? -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
