You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first added a JSON dependency to a library published under Maven Local, the Kotlin Jupyter kernel was unable to resolve the dependency until I added *mavenLocal to the repositories section of the JSON manifest. Does it make sense to add *mavenLocal as a default repository?
In general, using mavenLocal as default is a bad practice since it produces strange errors when you have different artifacts with the same version on remote and on local. I do not think it is a problem in the Jupyter environment since it is fluid. But I still think it is easier to turn it on with annotation.
When I first added a JSON dependency to a library published under Maven Local, the Kotlin Jupyter kernel was unable to resolve the dependency until I added
*mavenLocal
to the repositories section of the JSON manifest. Does it make sense to add*mavenLocal
as a default repository?Related to: #86
The text was updated successfully, but these errors were encountered: