Does not include Maven dependency
org.openrewrite.maven.search.DoesNotIncludeDependency
An applicability test which returns false if visiting a Maven pom which includes the specified dependency in the classpath of some scope. For compatibility with multimodule projects, this should most often be applied as a single-source applicability test.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite
artifactId: rewrite-maven
version: 8.23.1
Options
Type | Name | Description | Example |
---|---|---|---|
| groupId | The first part of a dependency coordinate |
|
| artifactId | The second part of a dependency coordinate |
|
| onlyDirect | Optional. Default false. If enabled, transitive dependencies will not be considered. |
|
| scope | Optional. Default any. If specified, only the requested scope's classpaths will be checked. Valid options: |
|
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.DoesNotIncludeDependencyExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.DoesNotIncludeDependencyExample
has been defined activate it in your build file:
Add the following to your
pom.xml
file:
Run
mvn rewrite:run
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
Nick McKinney, Jonathan Schnéider, Sam Snyder, Jonathan Leitschuh, Tim te Beek
Last updated