[Question] Java 25 support.

[galyfray]

Hi,
I just found the project and I am wondering if the JDK 25 is supported.

The readme states :

White-Box testing mode: can be used for APIs compiled to JVM (e.g., Java and Kotlin). EvoMaster analyses the bytecode of the tested applications, and uses several heuristics such as testability transformations and taint analysis to be able to generate more effective test cases. We support JDK 8 and the major LTS versions after that (currently JDK 21). Might work on other JVM versions, but we provide NO support for it. Note: there was initial support for other languages as well, like for example JavaScript/TypeScript and C#, but they were not in a stable, feature-complete state. The support for those languages for white-box testing has been dropped, at least for the time being.

Which hints that either you did not had time to update the readme since JDK 25 dropped or JDK 25 is currently not supported ( or not tested ?).

If JDK 25 is not supported what would need to be tackled for it support ?

[arcuri82]

hi @galyfray ,
thanks for your interest in EvoMaster.
The build fails in 25, but that might be due to some dependencies in the tests, not the tool itself.
If you use the evomaster.jar directly, it "might" work in 25, but haven't tested it.

[galyfray]

Okay, thank's for the information, i'll try to find some time to test the build process under Java 25.
If i manage to find any usefull information i'll add them here.

[arcuri82]

btw, i m curious, why do you need to build with JDK 25?
in black-box testing, programming language of API doesn't matter.
for white-box, instrumentation should still work, it is just that evomaster.jar "might" (haven't tested) need to be run differently with a different JDK (or more simply with pip install evomaster).
you do not need to build evomaster.jar locally (and if really do, could just use -DskipTests), you can just download it from release page

what is your use case?

[galyfray]

huh I think there is a missunderstanding. I want to run evomaster in white-box against a spring server compiled and ran with JDK 25.
So, I don't need per say to make it compile on JDK 25 I just understood that for it to work with an application under JDK25 reliably it would need to at least build on JDK 25.

[arcuri82]

hi,
for white-box, there are 2 processes to run:

1. the "driver", which needs some manual setup. This should work with JDK 25, unless there is some new breaking change in the JVM options in JDK 25 that need to be setup manually (ie, i haven't tested it).

2. the "core" evomaster.jar. That I know it fails to build in JDK 25, due to some test dependence. It "might" run with JDK 25 when you do java -jar evomaster.jar, but not sure. however, you can run a different JDK for the "core" than the API, as those are different processes. eg "pip install evomaster" does a local installation of JDK 17 for running the "core".

Unfortunately, we have other pressing matters to handle this month before checking for compatibility for JDK 25. but, as said, it "might" work if the JDK developers haven't decided to break more backward compatibility with JDK 25... (eg, 21 was ok, but 17 was a nightmare)

[galyfray]

Okay thank's for the clarification!
If I encounter any trouble while trying I'll add them to this discution and if I am able to fix them I'll make a PR 👍