Skip to content

Modernize the Gradle Plugin #388

@shanman190

Description

@shanman190

What problem are you trying to solve?

We receive issues from time to time about not supporting one or another Gradle feature properly, using the entire Gradle build as if it were a single project, not supporting configuration cache, inputs and outputs are missing in places, etc. All of this comes to a point when we're attempting to support such a large version range and as Gradle major versions introduce new defaults.

Describe the solution you'd like

We should really rewrite the plugin from the ground up such that it can work over a single project at a time, has all inputs and outputs modeled correctly, takes advantage of lazy task registration and property configuration, is compatible with configuration cache, etc.

Have you considered any alternatives or workarounds?

At some point we're going to run out of workarounds, so this is trying to stay ahead of that time.

Additional context

N/A

Are you interested in contributing this feature to OpenRewrite?

Always

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions