Skip to content

Commit 5877a38

Browse files
committed
Add explicit note on JSpecify support in Spring Framework 6.2 vs 7.0
Closes gh-34551
1 parent 94d29ba commit 5877a38

File tree

1 file changed

+10
-3
lines changed
  • framework-docs/modules/ROOT/pages/core/beans/annotation-config

1 file changed

+10
-3
lines changed

framework-docs/modules/ROOT/pages/core/beans/annotation-config/autowired.adoc

+10-3
Original file line numberDiff line numberDiff line change
@@ -444,9 +444,9 @@ through Java 8's `java.util.Optional`, as the following example shows:
444444
}
445445
----
446446

447-
You can also use a `@Nullable` annotation (of any kind in any package -- for example,
448-
`javax.annotation.Nullable` from JSR-305) or just leverage Kotlin built-in null-safety
449-
support:
447+
You can also use a parameter-level `@Nullable` annotation (of any kind in any package --
448+
for example, `javax.annotation.Nullable` from JSR-305) or just leverage Kotlin built-in
449+
null-safety support:
450450

451451
[tabs]
452452
======
@@ -477,6 +477,13 @@ Kotlin::
477477
----
478478
======
479479

480+
[NOTE]
481+
====
482+
A type-level `@Nullable` annotation such as from JSpecify is not supported in Spring
483+
Framework 6.2 yet. You need to upgrade to Spring Framework 7.0 where the framework
484+
detects type-level annotations and consistently declares JSpecify in its own codebase.
485+
====
486+
480487
You can also use `@Autowired` for interfaces that are well-known resolvable
481488
dependencies: `BeanFactory`, `ApplicationContext`, `Environment`, `ResourceLoader`,
482489
`ApplicationEventPublisher`, and `MessageSource`. These interfaces and their extended

0 commit comments

Comments
 (0)