Change Maven annotation processor path

org.openrewrite.java.micronaut.ChangeAnnotationProcessorPath

Change the groupId, artifactId, and version of a Maven annotation processor path.

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite.recipe

  • artifactId: rewrite-micronaut

  • version: 2.8.0

Options

TypeNameDescriptionExample

String

oldGroupId

The old groupId to replace. The groupId is the first part of a plugin coordinate 'com.google.guava:guava:VERSION'. Supports glob expressions.

org.openrewrite.recipe

String

oldArtifactId

The old artifactId to replace. The artifactId is the second part of a plugin coordinate 'com.google.guava:guava:VERSION'. Supports glob expressions.

my-deprecated-annotation-processor

String

newGroupId

Optional. The new groupId to use. Defaults to the existing group id.

corp.internal.openrewrite.recipe

String

newArtifactId

Optional. The new artifactId to use. Defaults to the existing artifact id.

my-new-annotation-processor

String

newVersion

Optional. An version string for the annotation processor path. Version strings that start with 'micronaut.' will be treated specially.

micronaut.validation

List

exclusions

Optional. A list of exclusions to apply to the annotation processor path in the format groupId:artifactId

io.micronaut:micronaut-inject

Data Tables

Source files that had results

org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

Column NameDescription

Source path before the run

The source path of the file before the run.

Source path after the run

A recipe may modify the source path. This is the path after the run.

Parent of the recipe that made changes

In a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.

Recipe that made changes

The specific recipe that made a change.

Estimated time saving

An estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.

Cycle

The recipe cycle in which the change was made.

Source files that errored on a recipe

org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

Column NameDescription

Source path

The file that failed to parse.

Recipe that made changes

The specific recipe that made a change.

Stack trace

The stack trace of the failure.

Recipe performance

org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

Column NameDescription

The recipe

The recipe whose stats are being measured both individually and cumulatively.

Source file count

The number of source files the recipe ran over.

Source file changed count

The number of source files which were changed in the recipe run. Includes files created, deleted, and edited.

Cumulative scanning time

The total time spent across the scanning phase of this recipe.

99th percentile scanning time

99 out of 100 scans completed in this amount of time.

Max scanning time

The max time scanning any one source file.

Cumulative edit time

The total time spent across the editing phase of this recipe.

99th percentile edit time

99 out of 100 edits completed in this amount of time.

Max edit time

The max time editing any one source file.

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.ChangeAnnotationProcessorPathExample. 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.ChangeAnnotationProcessorPathExample
displayName: Change Maven annotation processor path example
recipeList:
  - org.openrewrite.java.micronaut.ChangeAnnotationProcessorPath:
      oldGroupId: org.openrewrite.recipe
      oldArtifactId: my-deprecated-annotation-processor
      newGroupId: corp.internal.openrewrite.recipe
      newArtifactId: my-new-annotation-processor
      newVersion: micronaut.validation
      exclusions: io.micronaut:micronaut-inject

Now that com.yourorg.ChangeAnnotationProcessorPathExample has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-micronaut:2.8.0 in your build file:

  1. Add the following to your build.gradle file:

build.gradle
plugins {
    id("org.openrewrite.rewrite") version("6.16.4")
}

rewrite {
    activeRecipe("com.yourorg.ChangeAnnotationProcessorPathExample")
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-micronaut:2.8.0")
}
  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

Jeremy Grelle, Jonathan Schnéider, Tim te Beek

Last updated