From 9ad2bd563b001c0742d767fea9ddaaeb60400ec7 Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <r.zwitserloot@projectlombok.org>
Date: Wed, 8 Jan 2020 01:06:35 +0100
Subject: [fixes #788] lombok generated equals method plus a
 non-null-by-default annotation no longer clash.

---
 website/templates/features/EqualsAndHashCode.html | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'website/templates/features')

diff --git a/website/templates/features/EqualsAndHashCode.html b/website/templates/features/EqualsAndHashCode.html
index 5a7b8166..5b54e027 100644
--- a/website/templates/features/EqualsAndHashCode.html
+++ b/website/templates/features/EqualsAndHashCode.html
@@ -53,6 +53,8 @@
 		</p><p>
 			If a getter exists for a field to be included, it is called instead of using a direct field reference. This behaviour can be suppressed:<br />
 			<code>@EqualsAndHashCode(doNotUseGetters = true)</code>
+		</p><p>
+			If the class (or an enclosing class) has either the <code>@org.eclipse.jdt.annotation.NonNullByDefault</code> or the <code>@javax.annotation.ParametersAreNonnullByDefault</code> annotation, the parameter of the generated <code>equals</code> method will have the appropriate <code>@Nullable</code> annotation; JDK8+ is required when you do this. <span class="since">(since 1.18.12)</span>.
 		</p>
 	</@f.smallPrint>
 </@f.scaffold>
-- 
cgit