AVRO-4191 - include tests on JDK 25

[apupier]

What is the purpose of the change

(For example: This pull request improves file read performance by buffering data, fixing AVRO-XXXX.)

Verifying this change

(Please pick one of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Extended interop tests to verify consistent valid schema names between SDKs
• Added test that validates that Java throws an AvroRuntimeException on invalid binary data
• Manually verified the change by building the website and checking the new redirect

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[martin-g]

For some reason the Java SDK build and tests are not triggered ...

[apupier]

I do not think that we can use a matrix easily as the minimal Java version to do the compilation is JDK 21 but tests are launched with several JDKs versions. it is launched with different Maven execution directly defined in the pom.xml. Each version si picked from the toolchains.xml whcih is configured by the

[martin-g]

I do not think that we can use a matrix easily as the minimal Java version to do the compilation is JDK 21 but tests are launched with several JDKs versions. it is launched with different Maven execution directly defined in the pom.xml. Each version si picked from the toolchains.xml whcih is configured by the

OK!
I'll leave it to you. I haven't touched the Java SDK for a long time and obviously I have forgotten how it works.
Please revert whatever is needed.

[apupier]

I do not think that we can use a matrix easily as the minimal Java version to do the compilation is JDK 21 but tests are launched with several JDKs versions. it is launched with different Maven execution directly defined in the pom.xml. Each version si picked from the toolchains.xml whcih is configured by the

OK! I'll leave it to you. I haven't touched the Java SDK for a long time and obviously I have forgotten how it works. Please revert whatever is needed.

in fact, there are 2 ways of doing it.
Either set the minimal version to Java 17, use a matrix job and keep a single execution.
Or rely on toolchains. it is a bit more advanced, I think it will save time on Ci and it forces to have test splayed locally with all jdk by default. The downside is that it is more complicated to setup and seems that even committers on the project do not remember it.
So I think I will remove the different executions and reliance on the toolchain. (especially when I see that the jobs are already green now, it is just that we are playing the same tests several times with same JDKs and we cna go a bit faster)

[apupier]

it is surely possible to save the time mentioned here https://github.com/apache/avro/actions/runs/22854799208/job/66292172522?pr=3685#step:8:839 but to be honest, not sure it is worthy to take the risk to change too many things. The current PR should be enough as a first iteration.