From 816c0b99e7f0395b26f8a8c26e52110107f0b1e1 Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <reinier@zwitserloot.com>
Date: Wed, 23 Mar 2011 07:39:13 +0100
Subject: Updated documentation of XArgsConstructor to highlight that we
 won't/can't remove suppressConstructorProperties until GWT and Android get
 the CP annotation.

See issue #202
---
 website/features/Constructor.html | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/website/features/Constructor.html b/website/features/Constructor.html
index 072e46ed..c0ab9ef8 100644
--- a/website/features/Constructor.html
+++ b/website/features/Constructor.html
@@ -71,6 +71,10 @@
 				</p><p>
 					<code>@XArgsConstructor</code> can also be used on an enum definition. The generated constructor will always be
 					private, because non-private constructors aren't legal in enums. You don't have to specify <code>AccessLevel.PRIVATE</code>.
+				</p><p>
+					While <code>suppressConstructorProperties</code> has been marked deprecated in anticipation of a world where all java environments have the
+					<code>@ConstructorProperties</code> annotation available, first GWT 2.2 and Android 2.3.3, which do not (yet) have this annotation, will have
+					to be ancient history before this annotation parameter will be removed.
 				</p>
 			</div>
 		</div>
-- 
cgit