-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Unable to resolve dependencies #28
Comments
Hi @snowe2010, thank you for checking out Kotlin∇! It should be possible to use Maven, however I have not rigorously tested this setup so there may be errors. Can you try cloning this project and run |
Sure thing. After cloning that project and building (I set asdf to use a graalvm version of java17, but should still work the same) I get this error:
|
Since it looks like you're trying to explicitly use java 15 I set asdf to use |
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. |
@breandan it looks like the issue is with the maven artifact, though not sure why. It fails even if I use the artifact from maven central, so it's not an issue with our nexus repo. Here is an example app: |
from a cursory glance over the code it looks like you're not actually adding the jar to the publication, though I'm not sure how this is working with gradle then. I suspect it's due to gradle's metadata capabilities. |
You're probably right, it looks like something to do with how we're publishing our build artifact. I used to be a fan of Gradle, but after nearly a decade of fighting with it (e.g., #6, #26 in just this project) I've come to accept the fact that I do not understand Gradle and never will. Typically Gradle can resolve Maven dependencies written as:
But the fact that Maven cannot resolve Gradle artifacts published on Maven Central using the syntax:
indicates to me that something is definitely wrong with (1) either our Maven publication or (2) Gradle's dependency resolution mechanism or (3) possibly both. Thank you for reporting this issue! |
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? |
When using
I'm unable to resolve any ai types.
If I switch to
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?
The text was updated successfully, but these errors were encountered: