Skip to content

Specify project in wrapper update commandΒ #37761

Closed

Description

@ljacomet

Issue type

Wrong or misleading information

Problem description

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.

Page with the problem

https://docs.gradle.org/9.5.0/release-notes.html#upgrade-instructions

Activity

  1. hfhbd commented on May 2, 2026

    @hfhbd
    Contributor

    Also update the GitHub release notes.

  2. reinsch82 commented on May 5, 2026

    @reinsch82
    Member

    This is a valid documentation issue.

  3. devareddy05 commented on May 7, 2026

    @devareddy05
    Contributor

    Opened a PR for this: #37828

    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.

  4. self-assigned this
    on May 7, 2026
  5. added this to the 9.6.0 RC1 milestone on May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions