Gradle dependency insight

org.openrewrite.gradle.search.DependencyInsight

Find direct and transitive dependencies matching a group, artifact, and optionally a configuration name. Results include dependencies that either directly match or transitively include a matching dependency.

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite

  • artifactId: rewrite-gradle

  • version: 8.24.0

Options

TypeNameDescriptionExample

String

groupIdPattern

Group glob pattern used to match dependencies.

com.fasterxml.jackson.module

String

artifactIdPattern

Artifact glob pattern used to match dependencies.

jackson-module-*

String

version

Optional. Match only dependencies with the specified version. Node-style version selectors may be used.All versions are searched by default.

1.x

String

configuration

Optional. Match dependencies with the specified scope. If not specified, all configurations will be searched.

compileClasspath

Data Tables (Only available on the Moderne platform)

Dependencies in use

Direct and transitive dependencies in use.

Column NameDescription

Project name

The name of the project that contains the dependency.

Source set

The source set that contains the dependency.

Group

The first part of a dependency coordinate com.google.guava:guava:VERSION.

Artifact

The second part of a dependency coordinate com.google.guava:guava:VERSION.

Version

The resolved version.

Dated snapshot version

The resolved dated snapshot version or null if this dependency is not a snapshot.

Scope

Dependency scope. This will be compile if the dependency is direct and a scope is not explicitly specified in the POM.

Depth

How many levels removed from a direct dependency. This will be 0 for direct dependencies.

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.DependencyInsightExample. 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.DependencyInsightExample
displayName: Gradle dependency insight example
recipeList:
  - org.openrewrite.gradle.search.DependencyInsight:
      groupIdPattern: com.fasterxml.jackson.module
      artifactIdPattern: jackson-module-*
      version: 1.x
      configuration: compileClasspath

Now that com.yourorg.DependencyInsightExample 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.DependencyInsightExample")
}

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

Sam Snyder, Peter Streef, Jonathan Schnéider, Tim te Beek

Last updated