From 4b878f9ba996f852ce555c3024512ae34e34774e Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <reinier@zwitserloot.com>
Date: Fri, 23 May 2014 04:07:39 +0200
Subject: Added confkey to make @NonNull generate a different exception because
 of the IllegalArgumentException vs. NullPointerException that we really don’t
 want to get into.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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

(limited to 'website/features/NonNull.html')

diff --git a/website/features/NonNull.html b/website/features/NonNull.html
index 0e7d064d..4a98504a 100644
--- a/website/features/NonNull.html
+++ b/website/features/NonNull.html
@@ -42,6 +42,8 @@
 		<div class="overview confKeys">
 			<h3>Supported configuration keys:</h3>
 			<dl>
+			<dt><code>lombok.nonNull.exceptionType</code> = [<code>fully qualified name of an exception</code>] (default: <code>java.lang.NullPointerException</code>).
+			<dd>When lombok generates a null-check <code>if</code> statement, an exception is thrown, with the parameter / field name as message. By default, this will be a <code>java.lang.NullPointerException</code>, but you can for example put <code>java.lang.IllegalArgumentException</code> in this configuration key to have lombok throw a different exception.</dd>
 			<dt><code>lombok.nonNull.flagUsage</code> = [<code>warning</code> | <code>error</code>] (default: not set)</dt>
 			<dd>Lombok will flag any usage of <code>@NonNull</code> as a warning or error if configured.</dd>
 			</dl>
-- 
cgit