Skip to content

Align Spotless googleJavaFormat version in pom.xml #28

Description

@devops-thiago

Background

pom.xml pins the Spotless googleJavaFormat version to 1.17.0 (from the original scaffold). The workshop branches moved to 1.27.0, but main stayed on 1.17.0. Older google-java-format versions can format code differently from newer tooling (IDE plugins, other contributors), causing recurring Spotless check failures for contributors using newer formats.

Impact

  • Contributors using IDE formatting based on newer google-java-format may see mvn spotless:check fail with no code change of their own.
  • CI spotless:check and local formatting can disagree across versions, causing noise in PRs.

How to reproduce

  1. Run mvn spotless:check on main — passes with 1.17.0.
  2. Apply google-java-format 1.27+ to a file (e.g. via an IDE plugin).
  3. Run mvn spotless:check again — may now fail on formatting differences for that file.

Where the fix should land

Bump the googleJavaFormat version in pom.xml to a current release (e.g. 1.27.0, matching the workshop branches), run mvn spotless:apply, and commit any resulting formatting changes in the same PR so the tree stays green.

Files touched

  • pom.xml
  • Any .java files re-formatted by mvn spotless:apply

Acceptance criteria

  • pom.xml googleJavaFormat version is updated.
  • mvn spotless:check passes on the whole codebase.
  • CI code-quality job is green.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestjavaPull requests that update java code

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions