From 1e87b6dd7d4c0e046a17603aab636c8b4adf3289 Mon Sep 17 00:00:00 2001 From: Sebastien Deleuze Date: Sun, 24 Sep 2017 13:30:19 +0200 Subject: [PATCH] Update null-safety refdoc with jsr305 JAR guidelines --- src/docs/asciidoc/core/core-null-safety.adoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/docs/asciidoc/core/core-null-safety.adoc b/src/docs/asciidoc/core/core-null-safety.adoc index c4c9f1c4fd..36bbe252b1 100644 --- a/src/docs/asciidoc/core/core-null-safety.adoc +++ b/src/docs/asciidoc/core/core-null-safety.adoc @@ -16,8 +16,11 @@ in a generic way, without having to hard-code support for Spring annotations. [NOTE] ==== -It is not necessary with Kotlin 1.1.5+ nor recommanded to have JSR 305 dependency in user -project classpath. +It is not necessary nor recommanded to have JSR 305 dependency in project classpath to +take advatange of Spring null-safe API. Only projects like +Spring-based libraries using null-safety annotations in their codebase should add +`com.google.code.findbugs:jsr305:3.0.2` with `compileOnly` Gradle configuration or Maven +`provided` scope to avoid compile warnings. ==== They are also used by Kotlin which supports natively