You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wherever we recommend to invoke the wrapper task, we should use :wrapper to clearly indicate only the root project needs to be configured.
This is important for Configure on Demand and might play a role with Isolated Projects in the future.
Context (optional)
Release notes and the wrapper documentation might be impacted.
Updates wrapper task invocation examples from gradle wrapper / ./gradlew wrapper to :wrapper across Gradle docs, release-note templates, and CONTRIBUTING.md.
The unqualified form relies on root-project task lookup, which can break under Configure-on-Demand and is fragile with Isolated Projects.
This makes the recommended commands explicit, unambiguous, and forward-compatible.
Activity
hfhbd commentedon May 2, 2026
Also update the GitHub release notes.
reinsch82 commentedon May 5, 2026
This is a valid documentation issue.
devareddy05 commentedon May 7, 2026
Opened a PR for this: #37828
Updates wrapper task invocation examples from
gradle wrapper/./gradlew wrapperto:wrapperacross Gradle docs, release-note templates, andCONTRIBUTING.md.The unqualified form relies on root-project task lookup, which can break under Configure-on-Demand and is fragile with Isolated Projects.
This makes the recommended commands explicit, unambiguous, and forward-compatible.
Use the root-qualified `:wrapper` task (#1064)