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

Check if solver and solver Java API versions match during build #202

Open
arg0n1s opened this issue Jan 9, 2025 · 0 comments
Open

Check if solver and solver Java API versions match during build #202

arg0n1s opened this issue Jan 9, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@arg0n1s
Copy link
Collaborator

arg0n1s commented Jan 9, 2025

If there is a (major) version mismatch between the Solver implementation and the Solver Java API (e.g., GUROBI), the instantiation of the Solver will fail with a null pointer. Without background knowledge it is not clear why this happens, as no suitable error message is thrown that hints towards this version mismatch. In fact, such a message cannot be thrown since the JNI implementation of the GUROBI API does not check for errors and, thus, does not throw appropriate exceptions itself.

I suggest to check the version of the desired solver and the solver API provided by us during the build process. If the corresponding path variable is not set or references the wrong version, we will point this out.

@arg0n1s arg0n1s added the enhancement New feature or request label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant