Google Java Format Versions Save

What's Changed

• Passing --add-exports flags on the command line is no longer necessary for JDK 17 and newer (https://github.com/google/google-java-format/commit/ee81afc93990493701a6f7a2801eff058ac57891)

Full Changelog: https://github.com/google/google-java-format/compare/v1.14.0...v1.15.0

What's Changed

• Handle modifiers that start with non- (#696)
• Treat single-character upper case identifiers as UpperCamelCase, to improve formatting of Android R classes (16e72a1a9bbf182fac6686807e54bc846a9543ed)
• Don't format javadoc without a summary fragment as a single-line (668f108de438db15158d33ed1a386bdbab3b4d09)

Full Changelog: https://github.com/google/google-java-format/compare/v1.13.0...v1.14.0

What's Changed

• Fix formatting of pattern matching in switch when running on Java 17 (#689, #690)

Full Changelog: https://github.com/google/google-java-format/compare/v1.12.0...v1.13.0

What's Changed

• Format type annotation as part of the type, not part of the modifiers list (https://github.com/google/google-java-format/pull/653)
• Fix indentation of case statements on JDK 17 (https://github.com/google/google-java-format/pull/654)

Full Changelog: https://github.com/google/google-java-format/compare/v1.11.0...v1.12.0

google-java-format now has improved support for running on JDK 17 early access builds.

Changes:

• Handle final variables in instanceof patterns (#588)
• Fix handling of annotations in compact record constructors (#574)
• Fix a crash in instanceof pattern handling (#594)
• Wrap multiple values in switch expression case (#540)
• Fix formatting of module trees after JDK-8255464
• Support sealed classes (#603)

google-java-format now supports running on JDK 16. The following flags are required when running on JDK 16, due to JEP 396: Strongly Encapsulate JDK Internals by Default:

java \
  --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED \
  --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED \
  --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED \
  --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED \
  --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED \
  -jar google-java-format-1.10.0-all-deps.jar T...

Other changes:

• Handle extra ; in import lists (https://github.com/google/google-java-format/commit/b769e812a052d7cff4a2d86eff4981a5d358ee2d)
• Add missing space between unary - and negative literals (https://github.com/google/google-java-format/commit/6da736d786ac71a134ed6cc43e9cd825c83de0fd)
• Fix an off-by-one issue on the reflowing of string literals (https://github.com/google/google-java-format/commit/b9fd8d2242869ea7c9efd10cbbe7278c4b6611b1)

• Add support for yield statements (#489)
• Fix a crash in expression switches (#477)

Changes:

• The minimum supported runtime version is now JDK 11.
• Initial support for Java 14 language features, including preview features. (Only available when running the formatter on JDK 14 or newer.)
• Flag control of javadoc formatting (--skip-javadoc-formatting).
• Reflowing string literals that exceed the column limit.

Fixes

• Handle unary negation when formatting tabular arguments (#400)
• Remove trailing tabs from comments to make behavior idempotent (#422)
• Fix a crash on c-style arrays in parameters (#374)
• Fix import reorderer to handle single-line-comments in imports (https://github.com/google/google-java-format/commit/f24663829d503683c889ce77efa66ce8a1f24bb6)
• Handle double semi-colons after package statements (https://github.com/google/google-java-format/commit/5e114ca5f0486a336cdff9697b0910c16f5689c5)

Changes

• Treat expressions ending in .stream() as a syntactic unit
• Keep going if a file cannot be read, and report a non-zero exit status, similar to handling of syntax errors.

Features

• Don't format annotations as block-like constructs (#159)
• Add horizontal whitespace between varargs specifiers and type annotations (#282)
• Don't add spaces to //$NON-NLS-x$ comments (#221)
• Unify breaks between type parameters
• Add support for --assume-filename

Incompatible changes

• Version 1.6.1 of the IntelliJ plugin now notifies if google-java-format hasn't been configured for new projects. (Version 1.6.0 of the plugin enabled the formatter by default, but this behaviour was reverted in 1.6.1. See #290.)

Bug Fixes

• Don't crash on empty enum declarations (#281)
• Don't crash on unusual line separators (#201)