Remove a Gradle dependency

org.openrewrite.gradle.RemoveDependency

Removes a single dependency from the dependencies section of the build.gradle.

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite

  • artifactId: rewrite-gradle

  • version: 8.24.0

Options

TypeNameDescriptionExample

String

groupId

The first part of a dependency coordinate com.google.guava:guava:VERSION. This can be a glob expression.

com.fasterxml.jackson*

String

artifactId

The second part of a dependency coordinate com.google.guava:guava:VERSION. This can be a glob expression.

jackson-module*

String

configuration

Optional. The dependency configuration to remove from.

api

Usage

This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your rewrite.yml create a new recipe with a unique name. For example: com.yourorg.RemoveDependencyExample. Here's how you can define and customize such a recipe within your rewrite.yml:

rewrite.yml
---
type: specs.openrewrite.org/v1beta/recipe
name: com.yourorg.RemoveDependencyExample
displayName: Remove a Gradle dependency example
recipeList:
  - org.openrewrite.gradle.RemoveDependency:
      groupId: com.fasterxml.jackson*
      artifactId: jackson-module*
      configuration: api

Now that com.yourorg.RemoveDependencyExample has been defined activate it in your build file:

  1. Add the following to your build.gradle file:

build.gradle
plugins {
    id("org.openrewrite.rewrite") version("6.12.0")
}

rewrite {
    activeRecipe("com.yourorg.RemoveDependencyExample")
}

repositories {
    mavenCentral()
}
  1. Run gradle rewriteRun to run the recipe.

See how this recipe works across multiple open-source repositories

The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.

Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.

Contributors

Shannon Pamperl, Jonathan Schnéider, Josh Soref, Tim te Beek

Last updated