Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
[ID: 84651]
Select items in the list
[ID: 558956]
[ID: 874707]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
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: