Find relocated dependencies
org.openrewrite.java.dependencies.RelocatedDependencyCheck
_Find Maven and Gradle dependencies and Maven plugins that have relocated to a new groupId
or artifactId
. Relocation information comes from the oga-maven-plugin maintained by Jonathan Lermitage, Filipe Roque and others.
This recipe makes no changes to any source file by default. Add changeDependencies=true
to change dependencies, but note that you might need to run additional recipes to update imports and adopt other breaking changes._
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-java-dependencies
version: 1.7.0
Options
Type | Name | Description | Example |
---|---|---|---|
| changeDependencies | Optional. Whether to change dependencies to their relocated groupId and artifactId. |
Data Tables (Only available on the Moderne platform)
Relocated dependencies
A list of dependencies in use that have relocated.
Column Name | Description |
---|---|
Dependency group id | The Group ID of the dependency in use. |
Dependency artifact id | The Artifact ID of the dependency in use. |
Relocated dependency group id | The Group ID of the relocated dependency. |
Relocated ependency artifact id | The Artifact ID of the relocated dependency. |
Context | Context for the relocation, if any. |
Usage
This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-java-dependencies:1.7.0
in your build file or by running a shell command (in which case no build changes are needed):
Add the following to your
build.gradle
file:
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.
Last updated