-
-
Notifications
You must be signed in to change notification settings - Fork 343
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
Support Kotlin 2.0/Multiplatform artifacts during dependency resolution #3695
Comments
CC @alexarchambault. Do you think this something we could configure Coursier to do without patching it? Or would this functionality need to be added to Coursier itself? |
Coursier should support that, it's a matter of asking for the right types and extensions. I can have a look a bit later today. |
Probably it makes sense to add a bit more info on how Kotlin Multiplatform ecosystem works, it may be useful in the future for the artifact filtering. In fact, Kotlin Multiplatform heavily relies on the Gradle Module metadata (this is what gets published as When Kotlin Multiplatform publishes artifacts for multiple targets, it has target-specific modules + root module (described here). This can be seen on the example of The root artifact has the necessary metadata to point to the platform-specific artifacts (like
or even (if we are not building
and then if I have
And then target-specific artifact |
Thanks for the details @0xnm! We can definitely look at whether we can support the |
Follow up to #3611
The basic issue is that Coursier is unable to resolve Kotlin 2.0 dependencies, such as https://repo1.maven.org/maven2/org/jetbrains/kotlinx/kotlinx-html-js/0.11.0/. These dependencies do not contain
.jar
files, but instead contain.module
files and.klib
files:The success criteria is that after applying the following diff
The following command should not produce a compiler error:
The text was updated successfully, but these errors were encountered: