Change Maven plugin configuration
org.openrewrite.maven.ChangePluginConfiguration Apply the specified configuration to a Maven plugin. Will not add the plugin if it does not already exist in the pom.
- groupId: org.openrewrite
- artifactId: rewrite-maven
- version: 7.35.0
Type | Name | Description |
|---|---|---|
String | groupId | The first part of a dependency coordinate 'org.openrewrite.maven:rewrite-maven-plugin:VERSION'. |
String | artifactId | The second part of a dependency coordinate 'org.openrewrite.maven:rewrite-maven-plugin:VERSION'. |
String | configuration | Optional. Plugin configuration provided as raw XML. Supplying null will remove any existing configuration. |
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.ChangePluginConfigurationExample. 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.ChangePluginConfigurationExample
displayName: Change Maven plugin configuration example
recipeList:
- org.openrewrite.maven.ChangePluginConfiguration:
groupId: org.openrewrite.maven
artifactId: rewrite-maven-plugin
configuration: <foo>bar</foo>
Now that
com.yourorg.ChangePluginConfigurationExample has been defined activate it in your build file:Gradle
Maven
build.gradle
plugins {
id("org.openrewrite.rewrite") version("5.34.0")
}
rewrite {
activeRecipe("com.yourorg.ChangePluginConfigurationExample")
}
repositories {
mavenCentral()
}
pom.xml
<project>
<build>
<plugins>
<plugin>
<groupId>org.openrewrite.maven</groupId>
<artifactId>rewrite-maven-plugin</artifactId>
<version>4.39.0</version>
<configuration>
<activeRecipes>
<recipe>com.yourorg.ChangePluginConfigurationExample</recipe>
</activeRecipes>
</configuration>
</plugin>
</plugins>
</build>
</project>
Recipes can also be activated directly from the command line by adding the argument
-Drewrite.activeRecipes=com.yourorg.ChangePluginConfigurationExample
The Moderne public SaaS instance 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.