Change method access level

org.openrewrite.java.ChangeMethodAccessLevel

Change the access level (public, protected, private, package private) of a method.

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite

  • artifactId: rewrite-java

  • version: 8.23.1

Options

TypeNameDescriptionExample

String

methodPattern

A method pattern that is used to find matching method declarations/invocations.

org.mockito.Matchers anyVararg()

String

newAccessLevel

New method access level to apply to the method. Valid options: private, protected, package, public

public

Boolean

matchOverrides

Optional. When enabled, find methods that are overrides of the method pattern.

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.ChangeMethodAccessLevelExample. 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.ChangeMethodAccessLevelExample
displayName: Change method access level example
recipeList:
  - org.openrewrite.java.ChangeMethodAccessLevel:
      methodPattern: org.mockito.Matchers anyVararg()
      newAccessLevel: public

Now that com.yourorg.ChangeMethodAccessLevelExample has been defined activate it in your build file:

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

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

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

repositories {
    mavenCentral()
}
  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

Jonathan Leitschuh, Jonathan Schnéider, Tim te Beek

Last updated