Stop referring to old Spring versions in Javadoc

This commit is contained in:
Sam Brannen
2024-07-01 17:50:52 +02:00
parent e427ac2683
commit 932ce04541
26 changed files with 100 additions and 107 deletions

View File

@@ -29,7 +29,7 @@ import java.lang.annotation.Target;
* <em>Spring TestContext Framework</em>.
*
* <p>This annotation may also be used as a <em>meta-annotation</em> to create
* custom <em>composed annotations</em>. As of Spring Framework 5.1, a locally
* custom <em>composed annotations</em>. Note, however, that a locally
* declared {@code @BootstrapWith} annotation (i.e., one that is <em>directly
* present</em> on the current test class) will override any meta-present
* declarations of {@code @BootstrapWith}.

View File

@@ -46,8 +46,8 @@ import org.springframework.lang.Nullable;
* <p>This annotation may be used as a <em>meta-annotation</em> to create custom
* <em>composed annotations</em>.
*
* <p>As of Spring Framework 5.2, this annotation is only supported in conjunction
* with the {@link org.springframework.test.context.junit.jupiter.SpringExtension
* <p>This annotation is only supported in conjunction with the
* {@link org.springframework.test.context.junit.jupiter.SpringExtension
* SpringExtension} for use with JUnit Jupiter. Note that the {@code SpringExtension} is
* often automatically registered for you &mdash; for example, when using annotations such as
* {@link org.springframework.test.context.junit.jupiter.SpringJUnitConfig @SpringJUnitConfig} and

View File

@@ -1,5 +1,5 @@
/*
* Copyright 2002-2023 the original author or authors.
* Copyright 2002-2024 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.
@@ -30,13 +30,13 @@ import org.springframework.test.annotation.DirtiesContext.HierarchyMode;
* {@code TestContext} encapsulates the context in which a test is executed,
* agnostic of the actual testing framework in use.
*
* <p>As of Spring Framework 5.0, concrete implementations are highly encouraged
* to implement a <em>copy constructor</em> in order to allow the immutable state
* and attributes of a {@code TestContext} to be used as a template for additional
* contexts created for parallel test execution. The copy constructor must accept a
* single argument of the type of the concrete implementation. Any implementation
* that does not provide a copy constructor will likely fail in an environment
* that executes tests concurrently.
* <p>Concrete implementations are highly encouraged to implement a <em>copy
* constructor</em> in order to allow the immutable state and attributes of a
* {@code TestContext} to be used as a template for additional contexts created
* for parallel test execution. The copy constructor must accept a single argument
* of the type of the concrete implementation. Any implementation that does not
* provide a copy constructor will likely fail in an environment that executes
* tests concurrently.
*
* <p>As of Spring Framework 6.1, concrete implementations are highly encouraged to
* override {@link #setMethodInvoker(MethodInvoker)} and {@link #getMethodInvoker()}.