From 236c88fc5cb2444af353bec6370b43b915ed8fdb Mon Sep 17 00:00:00 2001
From: peichhorn <peichhor@web.de>
Date: Mon, 5 Sep 2011 21:53:58 +0200
Subject: fixed Issue 271: @NotNull annotations should introduce a null check

---
 website/features/GetterSetter.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'website')

diff --git a/website/features/GetterSetter.html b/website/features/GetterSetter.html
index 3e3530ef..51a1f514 100644
--- a/website/features/GetterSetter.html
+++ b/website/features/GetterSetter.html
@@ -58,7 +58,7 @@
 				Any variation on <code>boolean</code> will <em>not</em> result in using the <code>is</code> prefix instead of the <code>get</code> prefix; for example,
 				returning <code>java.lang.Boolean</code> results in a <code>get</code> prefix, not an <code>is</code> prefix.
 				</p><p>
-				Any annotations named <code>@NonNull</code> (case insensitive) on the field are interpreted as: This field must not ever hold
+				Any annotations named <code>@NonNull</code> or <code>@NotNull</code> (case insensitive) on the field are interpreted as: This field must not ever hold
 				<em>null</em>. Therefore, these annotations result in an explicit null check in the generated setter. Also, these
 				annotations (as well as any annotation named <code>@Nullable</code> or <code>@CheckForNull</code>) are copied to setter parameter and getter method.
 				</p><p>
-- 
cgit