fleetlint Policy for a fleet of repositories
v0.4
Getting started

format/configured/java

A formatter is configured

Implements format/configured for java.

Severitywarning
Tiers1, 2
Stacksjava
Scopeeach
Kindoutcome
Sourcelibrary v0.1.0
Selected byfleetlint-recommended@v0.1.0

Requirement

A formatter is wired into the build (this build, a parent build or a convention plugin): Spotless, google-java-format, Palantir Java Format or fmt-maven-plugin, or one runs in a hook, the task runner or CI. Another formatter is added with accept:.

Why

Without one formatter every editor reformats differently and diffs fill with whitespace churn that hides the real change.

Fix

Add Spotless with google-java-format (or Palantir) to the build and run spotless:check in the hooks.

Agent instruction: Add the Spotless plugin with googleJavaFormat() to the build, spotless:check to the lint target and a hook; reformat in a separate commit.

See: https://fleetlint.org/baseline/#static-analysis, https://fleetlint.org/stacks/#java


Generated by fleetlint docs from catalog v0.1.0.