1.7

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.

1.6

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)

1.5

Features:

• Improved support for checking if files are already formatted: --dry-run prints the paths of files whose contents would change if the formatter were run normally, and --set-exit-if-changed returns exit code 1 if there are any formatting changes. (#105)
• Added support for javac-style @params files. (#77).

Bug fixes:

• Improved partial formatting within switch statements (c63984a).
• Improved import ordering logic to handle imports not separated by newlines (7225e17, 8364f6c).

1.4

1.4 release

• initial support for Java 9 language features (effectively final variables in try-with-resources, module-info.java files).
• Remove java.lang imports
• Handle varargs lambda parameters
• Wrap line comments that exceed the column limit
• Ensure leading spaces are present in line comments (//comment -> // comment).
• Wrap before /*parameter=*/ comments.
• Handle type-annotated varargs.

1.3

1.3 release

1.2

1.2 release

1.1

1.1 release

1.0

google-java-format-1.0

1.0 release

0.1 Alpha

Early release of Google's Java Formatter for use in formatting code to google's style.