-
Notifications
You must be signed in to change notification settings - Fork 4
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
An older jar is used instead of the one indicated in %%loadFromPOM #31
Comments
Hi Pavel, thanks for reporting the problem. Feels like one of the many issues with Ivy (the current dependency management engine we inherited from iJava). I'll try to reproduce and see if there's a a fix. On the longer run we'll switch to Maven for this (see #23). FWIW, there's a somewhat heavy-handed and hackish way to resolve at least some of the dependency issues: |
Hi Andrus, Thank you for letting me know! |
Ah, everything is simpler than I thought. The base Jupyter kernel that JJava uses has a transitive dependency on |
That's an interesting root cause :). Thank you for discovering it! |
|
While debugging the milvus-io/milvus-sdk-java#1040 issue I found out that JJava is using a random jar version for some reason.
Here is the reproduction:
The error:
So, the 2.8.5 or older version is used in fact. The same code works fine if run as a normal Java SE application.
The text was updated successfully, but these errors were encountered: