Skip to content

Conversation

@ghaliouss
Copy link
Contributor

No description provided.

@ghaliouss ghaliouss self-assigned this Jul 21, 2025
@ghaliouss ghaliouss linked an issue Jul 21, 2025 that may be closed by this pull request
@davidouagne
Copy link
Member

The Java version check is good, but why enforce Java 21 when Matchbox still supports Java 11?

@ghaliouss
Copy link
Contributor Author

The Java version check is good, but why enforce Java 21 when Matchbox still supports Java 11?

Hello @davidouagne , The current version of the matchbox project uses JDK 21 and is compiled with Java 21, as specified by <maven.compiler.release>21</maven.compiler.release> in the Maven configuration.
However, the documentation has not yet been updated it seems.

image

@davidouagne
Copy link
Member

Do you know if it’s possible to build Matchbox with an earlier version such as Java 17?

Is it possible to configure a CI/CD pipeline with the Java version as a parameter?

It may be necessary to have good control over the Java version, as other users are using Java 17 instead of 21.

@Rosnyni
Copy link
Collaborator

Rosnyni commented Aug 25, 2025

There is a warning message when using java 17 :

image

and validation don't work, but everything work well with java 21.

@ghaliouss ghaliouss merged commit 51bd11c into main Aug 26, 2025
1 check passed
@ghaliouss ghaliouss deleted the 11-upgrade-matchbox-engine-to-v401 branch August 28, 2025 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

upgrade matchbox-engine to v4.0.1

4 participants