Fixed
Status Update
No update yet.
Comments
ga...@google.com
ga...@google.com
As I understand it, we need to migrate namespace definitions both from AndroidManifest.xml and from implicit definitions from applicationId / testApplicationId? Is that right? So an 8.0 project would have a
namespace <n>
testNamespace <tn>
where <n> is taken from AndroidManifest.xml package definitions if present, and applicationId if not, and <tn> is testApplicationId if present and <n>.test if not?
Description
DESCRIBE THE ISSUE IN DETAIL:
In Gradle 7.1,
org.gradle.util.ConfigureUtilhas been soft deprecated (@Deprecatedannotation).For Gradle 7.6 we wanted to add deprecation nagging to it. Our smoke tests show that the Android Gradle Plugin still uses the
ConfigureUtil.configure(closure, target)function in >= 7.4. We will postpone adding the deprecation nagging because users currently cannot resolve it.Could you please look into removing that usage from the Android Gradle Plugin?
Studio Build: Version of Gradle Plugin: 7.4 Version of Gradle: Version of Java: OS: