This message was deleted.
# community-support
s
This message was deleted.
🤣 1
t
Have you tried with
--stacktrace
?
v
As these are not Gradle deprecation warnings but AGP deprecation warnings, I guess that option will not help. In that case, set a breakpoint in the mentioned method and debug the build, then you should see where the call is coming from.
v
hmm, set a breakpoint where exactly? trouble is there is nothing special in those modules, just android library, kotlin-android applied
v
In the method it complains about.
BasePlugin.getExtension()
v
Uhm, you mean like in gradle's own source somehow? It's not my method, this is all there is to the given build.gradle
Copy code
apply plugin: "com.android.library"
apply plugin: "kotlin-android"
apply plugin: "com.squareup.anvil"

anvil {
    generateDaggerFactories.set(true)
}

dependencies {
    implementation deps.conductor
    implementation deps.androidx.ktx
    implementation deps.androidx.constraintLayout
    implementation deps.dagger.runtime
    implementation deps.coroutines.core


    implementation project(":radost:onboarding:data:contract")
    ...
    implementation project(":base")

    testImplementation deps.test.junit
}
v
Again, this is neither a Gradle deprecation warning, nor a Gradle method. It is from the Android Gradle Plugin. But yeah, I'm aware that it is not your method. But that doesn't prevent you from setting a breakpoint.
b
With something as standard as the AGP, I believe it's safe to assume that the Gradle-8 compatible AGP, which will come out at the same time as Gradle-8, will have this resolved.
v
I tend to doubt it. 😄 AGP complains that something is calling a method of it that will fail once AGP is on version 8. If that piece that is calling the deprecated method in AGP is not updated to be compatible it will just fail. Hence it makes perfectly sense to find out who it is and to report it as problem.
v
I might be stupid but how do I set a break point in build script? Do I need to attach debugger to the kotlin daemon and all that hacky jazz?
v
No, nothing hacky necessary, IntelliJ does all for you. Just set the breakpoint and press on debug.