Most programmers agree that having consistent formatting across a code base makes it easier to work with. Tools like Checkstyle provide automated enforcement of these policies. But it's never fun to have your workflow interrupted by complaints about formatting. This guide will show you how to configure rewrite to automate the remediation of Checkstyle policy violations.
Example Configuration
How you configure Checkstyle integration depends on whether or not your build also applies a Checkstyle plugin. For Gradle builds this means the built-in plugin named Checkstyle Plugin. For Maven builds this means maven-checkstyle-plugin.
With Checkstyle Plugin
If your build uses either the Gradle or Maven checkstyle plugins, then good news, the rewrite build plugins will detect that and automatically match their configuration. All that remains is to activate the Code cleanup recipe. Activating that recipe in your build file and running rewrite is all you need to do to begin auto-remediating Checkstyle policy violations.
mavenCentral()// rewrite is published to Maven Central
13
}
Copied!
At this point, you're ready to fix Checkstyle policy violations by running mvn rewrite:run or gradlew rewriteRun.
OpenRewrite can be configured to use different checkstyle policies than your Checkstyle plugin. Follow the "No Checkstyle Plugin" instructions to override the location of the checkstyle configuration file.
No Checkstyle Plugin
If your build does not use either of the Gradle or Maven Checkstyle plugins, you can still configure the rewrite build plugins to use a checkstyle xml configuration file.
mavenCentral()// rewrite is published to Maven Central
13
}
Copied!
At this point, you're ready to fix Checkstyle policy violations by running mvn rewrite:run or gradlew rewriteRun.
Applying Refactors before Checkstyle
Depending on exactly how your build is configured, it might run Checkstyle before OpenRewrite. So the Checkstyle tool might report violations that would be fixed if your build were to run OpenRewrite first.
With this configuration, rewrite refactoring will be run as part of any build that runs checkstyle.
Gradle
In Gradle, Task.dependsOn() can be used to ensure that invoking one task always causes another task to run first. That means making all tasks of type org.gradle.api.plugins.quality.Checkstyle depend on the rewriteRun task provided by the OpenRewrite plugin.
mavenCentral()// rewrite is published to Maven Central
14
}
15
​
16
// In older versions of gradle, use tasks.get() instead instead of tasks.named()
17
def rewriteRunTask = tasks.named("rewriteRun")
18
​
19
// In a kotlin build script, use tasks.withType<Checkstyle>()
20
tasks.withType(Checkstyle){
21
dependsOn(rewriteRunTask)
22
}
Copied!
Maven
In Maven, the ordering of goals depends first on which phase of the Build Lifecycle they are declared in, then secondarily by the order in which plugins are declared. This means that the rewrite-maven-plugin should be declared above the maven-checkstyle-plugin in your pom.xml and configured to execute within the same phase as you configure checkstyle to run its "check" goal.
We don't have OpenRewrite recipes implemented for all publicly available policies. If you find a checkstyle policy violation you'd like automated, visit the rewrite repository and file an issue.
Checkstyle configuration loading only informs the behavior of recipes, not which recipes are active. Regardless of the presence or non-presence of Checkstyle configuration, OpenRewrite will never apply any refactoring you do not explicitly activate.