Hi Nanda,
On using Java 11 ozone builds - It should be noted that when running our
dev-support findbugs script on the build I found it generates many findings
(NULL related) that are not reported when run on Java 8 compiled build.
Generally, I look for a clean findbugs pass on a Java 8 build to a
Thanks for taking a look at this Attila.
Even though we use Java 11 for compilation, the binaries are generated for
Java 8.
This is because we have mentioned it in the pom file
*1.8*
In this scenario, JDK 11 compiles Ozone code and generates binary
targeting Java 8.
If we update the Java versio
Hi Nanda,
> Currently, we compile and verify Ozone only with Java 8. As far as I know,
> we haven't tested Ozone either with Java 11 or 17.
CI compiles each commit with both Java 8:
https://github.com/apache/ozone/blob/d6f63bf2e53ac8a4220ee829d8bbb2427dd7d3fa/.github/workflows/ci.yml#L60-L68
http
Hi All,
Currently, we compile and verify Ozone only with Java 8. As far as I know,
we haven't tested Ozone either with Java 11 or 17.
We should start compiling and testing Ozone with higher versions of Java to
make the version upgrade easier in the future.
This will enable us to upgrade the Java
