Unable to resolve dependencies
See original GitHub issueWhen using
<dependency>
<groupId>ai.hypergraph</groupId>
<artifactId>kotlingrad</artifactId>
<version>0.4.7</version>
</dependency>
I’m unable to resolve any ai types.
If I switch to
<dependency>
<groupId>ai.hypergraph</groupId>
<artifactId>kotlingrad-jvm</artifactId>
<version>0.4.7</version>
</dependency>
instead, I get failures to resolve kotlin-bom
Unresolved dependency: 'org.jetbrains.kotlin:kotlin-bom:jar:1.6.10'
Currently it seems impossible to use this project with the current pom setup. Do you have an example of an external project using kotlingrad where this works?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Unable to resolve dependency for ':app@debug ...
23 Answers 23 · Ensure that your Android Studio does not need to go through any proxy. · Export the certificate where you...
Read more >Unable to resolve dependencies of NuGet packages
Clear the NuGet cache files. You do this in the following way: In the toolbar of Visual Studio, navigate to Tools » NuGet...
Read more >Android Studio “Unable to resolve dependency” Error
The most of users encounter errors like “Unable to resolve dependency for ':app@debug/ compileClasspath': Could not find any
Read more >Unable to resolve dependency tree error in Angular while ...
To fix Unable to resolve dependency tree error in Angular while installing `npm` packages follow the below steps. 1.
Read more >(Solved) ERESOLVE unable to resolve dependency tree ...
Solution · 1. Remove node_modules and package-lock.json and then run · 2. Or try clearing out npm cache · 3. Or run command...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, seeing something really weird. I wipe your artifact from my .m2 repo and then the gradle build works fine.
As soon as I try to build using maven it fails. I believe this might be related to our nexus repository. I’ll get back to you in a bit.
Yes, Gradle can be quite difficult to use, though I do like it more than Maven for most use cases. Looking at your build.gradle though, it is quite complex, so I would expect some issues with that. I don’t completely understand everything you’re doing, especially with the git submodules and this shipshape library. I think most of the issues here are coming from your use of kotlin multiplatform. Have you tried following along with how a project like kotest does multiplatform?