I would classify the must things into:
1. CI infrastructure.
We must refactor the CI to supply regular checks for JDK 17, in both compiling
and testing.
In my local play, I can compile the Hadoop code successful with tune some maven
plugin args, while the CI for testing is a little bit challengi
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1654/
[Jul 29, 2024, 10:33:51 AM] (github) HADOOP-19161. S3A: option
"fs.s3a.performance.flags" to take list of performance flags (#6789)
[Jul 29, 2024, 6:45:14 PM] (github) HADOOP-19238. Fix create-releas
> One thing I know is that it is necessary to upgrade JUnit 4 to JUnit 5
Do you know any specific reason or docs mentioning that? Just curious
as to why we need to migrate to JUnit 5 for JDK-17, Looking here [1],
it seems like it supports JDK-21 as well and even [2] mentions like it
does support
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1469/
No changes
-1 overall
The following subsystems voted -1:
asflicense hadolint mvnsite pathlen unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
