Open jimgoog opened 3 years ago
Gradle will ignore the POMs and use the .module
metadata file for resolution, which is probably why it works in Gradle. The files
array looks like it specifies .jar
dependencies and each variant is specifying the "org.gradle.libraryelements": "jar"
attribute so that's the artifact that's resolved at build time.
I think we should write the right type ("jar"). Even if "aar" works, it is not right :).
Is it something to be fixed in publishing task, right?
Is it something to be fixed in publishing task, right?
Yes, probably here: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:buildSrc/src/main/kotlin/androidx/build/MavenUploadHelper.kt;l=227;bpv=0
This is still a blocking issue with 1.0.0-beta5 from Maven Central using other build systems than Gradle.
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.
Looking at the dependencies of many of the maven artifacts (eg. https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/desktop/desktop/0.3.2/desktop-0.3.2.pom) we see that dependencies are declared like:
But this is really weird because desktop does not use aars and so specifying the type as such can confuse the build systems.