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
Could not resolve all task dependencies for configuration #1108
Comments
Just for the record, I've now submitted a bug report for the solution stated by the official documentation. Hopefully it will get fixed, but it might still be worth figuring out why the other setup mentioned above doesn't work. |
I think that other configuration you create needs to have some metadata attached to it. If you provide a reproducer I can take a look and see if there's something I can do in DAGP. |
@autonomousapps here we go: Thanks! |
I've just resolved another issue that looks at least superficially similar. Could you try the latest snapshot (wait at least an hour from when I post this message)? |
Hey @autonomousapps, Thanks for the update. Unfortunately, I've tested |
Alright, thanks! Looks like something that might be Android-specific. |
I was able to workaround this by adding this to the top of the "wrapper" module: // wrapper-module/build.gradle
plugins {
id("java")
} I find the existence of such modules unusual -- what's the use-case? Why not just add the jar as a dependency to "normal" modules directly? |
For Android projects, it throws a lint error since adding AAR files directly misses the non-JVM parts of the archive. |
What exactly throws a lint error? |
Plugin version
1.28.0 (and 1.29.0)
Gradle version
8.2
JDK version
17
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
Kotlin 1.9.21
(Optional) Android Gradle Plugin (AGP) version
8.2.1
Describe the bug
After bumping to 1.28.0 we get this error when building the project (for instance via
build
):moduleA
is here a regular module (with plugincom.android.library
) andmoduleB
is a "wrapper" around an AAR file to be able to use it. The AAR file is included like this:This is not how the official documentation states it, but due to a weird bug this doesn't work for other reasons unfortunately.
I don't know if we can fix this in any other ways (is it possible to ignore dependencies or modules somehow?), so wanted to file this bug if you weren't aware of this. And for the record, it works fine for version 1.27.0.
The text was updated successfully, but these errors were encountered: