Stop referring to features as "Java 5" features

With a Java 8 baseline in place for quite some time now, it no longer
makes sense to refer to features such as annotations as "Java 5
annotations".

This commit also removes old `Tiger*Tests` classes, thereby avoiding
duplicate execution of various tests.
This commit is contained in:
Sam Brannen
2022-03-18 16:32:30 +01:00
parent 1419172fbd
commit 64b64d9ba0
27 changed files with 598 additions and 710 deletions

View File

@@ -1,5 +1,5 @@
/**
* Support package for beans-style handling of Java 5 annotations.
* Support package for beans-style handling of annotations.
*/
@NonNullApi
@NonNullFields

View File

@@ -1,5 +1,5 @@
/*
* Copyright 2002-2021 the original author or authors.
* Copyright 2002-2022 the original author or authors.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
@@ -44,7 +44,7 @@ import org.springframework.util.Assert;
/**
* {@link org.springframework.beans.factory.config.BeanPostProcessor} implementation
* that enforces required JavaBean properties to have been configured.
* Required bean properties are detected through a Java 5 annotation:
* Required bean properties are detected through an annotation:
* by default, Spring's {@link Required} annotation.
*
* <p>The motivation for the existence of this BeanPostProcessor is to allow