Skip to content

Fix Gradle use of version catalogs for special cases #533

@binkley

Description

@binkley

Context

Working on #498, two special cases arise for Gradle plugin dependencies:

  • The plugin "ships" with Gradle installs (eg, "checkstyle")
  • The plugin has independent versioning for an underlying tool (eg, "pmd")

Rather than hold up #498 which already satisfies the acceptance criteria ("GH dependabot makes Gradle PRs"), break the specialized work out to a separate card, this one.

Tech context

  • Decide if to migrate plugins bundled with Gradle that they use the version catalog in the build
  • For plugins with a separate "toolVersion" property for independent versioning of a tool and its plugin, manage updates separately
  • For bundled plugins, manage "toolVersion" (there is overlap between tasks 1 and 2)
  • In all cases, update the wiki page docs to reflect what users should do (both in their Gradle scripts, and version-checking tasks on the command line)

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency file

    Projects

    Status

    Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions