Skip to content

Prepare for Gradle 7 deprecation #358845

Open
@tomodachi94

Description

It is reasonable to assume that Gradle 9 will release soon (likely within the next two release cycles). As Gradle 7 is now the oldest-supported version of Gradle, it will become EOL when this happens. We cannot reasonably support Gradle 7 once it goes completely end-of-life.

How to help

Below is a list of in-tree consumers.

For each:

  • Check if it builds with the latest version of Gradle.
    • If it does, update references from gradle_7 to:
      • gradle_8 (if it relies on features that will be removed in Gradle 9; there should be a warning in the build log if this is the case)
      • gradle (if it does not rely on features scheduled for removal).
    • If it doesn't build with a newer Gradle, attempt to write a patch.
      • Submit it upstream first, especially if upstream is active; the idea is that the fix would be included in the next release of the software, making a special Nixpkgs patch unnecessary and overall contributing to the health of the ecosystem.
      • If upstream is unresponsive and hasn't merged the PR by the time Gradle 9 is released, apply the patch locally.

The list

Metadata

Assignees

No one assigned

    Labels

    0.kind: enhancementAdd something new2. status: backlogThis is a low priority3.skill: sprintableA larger issue which is split into distinct actionable tasks5. scope: trackingLong-lived issue tracking long-term fixes or multiple sub-problems6.topic: javaIncluding JDK, tooling, other languages, other VMs6.topic: old-versionsTickets pertaining to ongoing support of outdated versions of packages

    Type

    No type

    Projects

    • Status

      Tracking

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions