org.openrewrite.gradle.ChangeDependency
Change a Gradle dependency coordinates.
GitHub, Issue Tracker, Maven Central
- groupId: org.openrewrite
- artifactId: rewrite-gradle
- version: 8.1.3
Type | Name | Description |
---|---|---|
String |
oldGroupId | The old groupId to replace. The groupId is the first part of a dependency coordinate 'com.google.guava:guava:VERSION'. Supports glob expressions. |
String |
oldArtifactId | The old artifactId to replace. The artifactId is the second part of a dependency coordinate 'com.google.guava:guava:VERSION'. Supports glob expressions. |
String |
newGroupId | Optional. The new groupId to use. Defaults to the existing group id. |
String |
newArtifactId | Optional. The new artifactId to use. Defaults to the existing artifact id. |
String |
newVersion | Optional. An exact version number or node-style semver selector used to select the version number. |
String |
versionPattern | Optional. Allows version selection to be extended beyond the original Node Semver semantics. So for example,Setting 'version' to "25-29" can be paired with a metadata pattern of "-jre" to select Guava 29.0-jre |
Parameter | Value |
---|---|
oldGroupId | commons-lang |
oldArtifactId | commons-lang |
newGroupId | org.apache.commons |
newArtifactId | commons-lang3 |
newVersion | 3.11.x |
versionPattern | null |
{% tabs %} {% tab title="build.gradle" %}
{% code title="build.gradle" %}
plugins {
id "java-library"
}
repositories {
mavenCentral()
}
dependencies {
implementation "commons-lang:commons-lang:2.6"
}
{% endcode %}
{% code title="build.gradle" %}
plugins {
id "java-library"
}
repositories {
mavenCentral()
}
dependencies {
implementation "org.apache.commons:commons-lang3:3.11"
}
{% endcode %}
{% endtab %} {% tab title="Diff" %} {% code %}
--- build.gradle
+++ build.gradle
@@ -10,1 +10,1 @@
dependencies {
- implementation "commons-lang:commons-lang:2.6"
+ implementation "org.apache.commons:commons-lang3:3.11"
}
{% endcode %} {% endtab %} {% endtabs %}
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.ChangeDependencyExample
.
Here's how you can define and customize such a recipe within your rewrite.yml:
{% code title="rewrite.yml" %}
---
type: specs.openrewrite.org/v1beta/recipe
name: com.yourorg.ChangeDependencyExample
displayName: Change Gradle dependency example
recipeList:
- org.openrewrite.gradle.ChangeDependency:
oldGroupId: org.openrewrite.recipe
oldArtifactId: rewrite-testing-frameworks
newGroupId: corp.internal.openrewrite.recipe
newArtifactId: rewrite-testing-frameworks
newVersion: 29.X
versionPattern: '-jre'
{% endcode %}
Now that com.yourorg.ChangeDependencyExample
has been defined activate it in your build file:
{% tabs %}
{% tab title="Gradle" %}
{% code title="build.gradle" %}
plugins {
id("org.openrewrite.rewrite") version("6.1.4")
}
rewrite {
activeRecipe("com.yourorg.ChangeDependencyExample")
}
repositories {
mavenCentral()
}
{% endcode %} {% endtab %}
{% endtabs %}
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.