Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate the feasibility of setting up CI builds/tests with another JDK #369

Open
cyrille-artho opened this issue Jul 10, 2023 · 2 comments
Labels
java version Java version

Comments

@cyrille-artho
Copy link
Member

To reproduce the build/test failures we have on some systems, we currently use a local build. It would be desirable to have another build pipeline on CI to automate this task.
It is not sure if that is feasible due to licensing issues; can someone please investigate this?
As a starter, we want to see exactly which package needs to be used to reproduce the problems with the remaining two unit tests.

@cyrille-artho
Copy link
Member Author

With a quick search, I could only find ways to set up Oracle Java version 17 and later.
Perhaps we can try to fix the current (very few) issues with version 11 by testing offline, once all the other version 11-related issues are resolved. After that, we can try out version 17, the next LTS version after 11.

@cyrille-artho
Copy link
Member Author

Another way to deal with this is to make the code compilable against Oracle's JDK v11 but without fully implementing the functionality that is covered by the failing tests. The few tests that fail can then be run conditionally (skipping them for OpenJDK): https://www.baeldung.com/junit-5-conditional-test-execution

@cyrille-artho cyrille-artho added the java version Java version label Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
java version Java version
Projects
None yet
Development

No branches or pull requests

1 participant