[issue #2039] update docs to warn about a javac peculiarity for named static imports.

1 files changed, 2 insertions, 0 deletions

diff --git a/website/templates/features/Builder.html b/website/templates/features/Builder.html
index 793c7b54..082b97ed 100644
--- a/website/templates/features/Builder.html
+++ b/website/templates/features/Builder.html
@@ -183,6 +183,8 @@ public class JacksonExample {
 			The initializer on a <code>@Builder.Default</code> field is removed and stored in a static method, in order to guarantee that this initializer won't be executed at all if a value is specified in the build. This does mean the initializer cannot refer to <code>this</code>, <code>super</code> or any non-static member. If lombok generates a constructor for you, it'll also initialize this field with the initializer.
 		</p><p>
 			Various well known annotations about nullity cause null checks to be inserted and will be copied to parameter of the builder's 'setter' method. See <a href="/features/GetterSetter">Getter/Setter</a> documentation's small print for more information.
+		</p><p>
+			Due to a peculiar way javac processes static imports, trying to do a non-star static import of the static <code>builder()</code> method won't work. Either use a star static import: `import static TypeThatHasABuilder.*;` or don't statically import the <code>builder</code> method.
 		</p>
 	</@f.smallPrint>
 </@f.scaffold>