0.3.14

Type	Description	Link
Fix	Method chains in initializers may once again be laid onto a single next line, if they are short enough. This fixes a regression from #123 (0.3.11) where the column limit for method chains would prevent us from attempting to put the initializer on the 2nd line first and see if that works.	#138

0.3.13

Type	Description	Link
Fix	Re-allow wrapping long inline tags like {@link from the 2nd whitespace onwards.	#131

0.3.12

Type	Description	Link
Improvement	In javadocs, keep inline tags like {@link ...} on the same line if not already split.	#125

0.3.11

Type	Description	Link
Fix	Nested method chains now also adhere to column limit.	#123

0.3.10

Type	Description	Link
Improvement	When importing a gradle project with com.palantir.java-format-idea from IntelliJ, eagerly configure the necessary XML files in .idea rather than relying on unwieldy IntelliJ task triggers.	#120

0.3.9

Type	Description	Link
Improvement	A new plugin com.palantir.java-format-spotless configures gradle-spotless (if applied) to format java files using palantir-java-format. The main com.palantir.java-format plugin now applies both the spotless and idea plugins too.	#107

0.3.8

Type	Description	Link
Fix	No longer break string concats unless they are a method's only argument on the line so far.	#104

0.3.7

Type	Description	Link
Fix	Partially inlined levels are now also limited such that the last dot in method call chains can't exceed 80 characters.	#101

0.3.6

Type	Description	Link
Improvement	Never put field annotations on the same line as the field declaration.	#102

0.3.5

Type	Description	Link
Fix	Bring back inlining the prefix of method calls iff the levels inlined so far have all been simple. This fixes the regression introduced in 0.3.4 where long nested method calls would end up with too many indents.	#99