Skip to content
This repository has been archived by the owner on Jan 28, 2023. It is now read-only.

How to use a specific krangl version in Jupiter with Kotlin kernel? #119

Closed
alshan opened this issue Mar 22, 2021 · 4 comments
Closed

How to use a specific krangl version in Jupiter with Kotlin kernel? #119

alshan opened this issue Mar 22, 2021 · 4 comments

Comments

@alshan
Copy link

alshan commented Mar 22, 2021

%use krangl(0.15.7)

results in error:

Failed to resolve com.github.holgerbrandl:krangl:0.15.7:
File 'com.github.holgerbrandl:krangl:0.15.7' not found
unresolved dependency: com.github.holgerbrandl#krangl;0.15.7: not found

@LeandroC89
Copy link
Contributor

LeandroC89 commented Mar 26, 2021

Hello Igor,
You're using it right as that is how I use it too, however the latest version I'm able to use is 0.15.3, not sure it'll have everything you need but it is working nicely.

%use krangl(0.15.3)

From 0.15.4 upwards I've faced a similar issue, mine just varies a bit.

Failed to resolve de.mpicbg.scicomp:krangl:0.15.7:
File 'de.mpicbg.scicomp:krangl:0.15.7' not found
unresolved dependency: de.mpicbg.scicomp#krangl;0.15.7: not found

@alshan
Copy link
Author

alshan commented Mar 26, 2021

I see, thank you!

@holgerbrandl
Copy link
Owner

Since jcenter is going down, I moved krangl to maven-central. This required to change the group-id from de.mpicbg.scicomp to com.github.holgerbrandl.krangl, which is subsequently simplified to com.github.holgerbrandl.krangl (starting with 0.15.8).

This should fix jupyter usage with the current definition https://github.com/Kotlin/kotlin-jupyter/blob/master/libraries/krangl.json with 0.15.8 and higher. If not I'll prepare a PR on the file to fix it.

I'm not able to port all old versions from jcenter to maven-central unfortunately. Sorry for that.

@LeandroC89
Copy link
Contributor

Thanks, it worked for me with 0.15.8

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants