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
+1 (non-binding)
Thanks Nicholas for working on this.
-Nilotpal Nandi
On Tue, 13 Dec, 2022, 3:31 pm Attila Doroszlai,
wrote:
> +1
>
> -Attila
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
> For additional
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
+1
-Attila
-
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
+1 (non-binding)
* Verified the checksums and signature
* Commit hash matches the git tag
* Build from source successful
* Started a cluster using binary package
* Tested RATIS and EC write/read/delete with freon ockg/ockv/ockr
* Tested ozone fs -ls in legacy bucket when '/' in key name.
* Tested
+1
- Verified all checksums and signatures.
- Checked LICENSE.txt and NOTICE.txt.
- Compared the files in the src tarball with the files in git.
- Built from source successfully.
- Able to run yarn job with docker.
Job Finished in 28.312 seconds
Estimated value of Pi is 3.14146667
