Deprecate support for custom, default ContextLoader class name in the TestContext framework [SPR-11682]

[spring-projects-issues]

Sam Brannen opened SPR-11682 and commented

Overview

#14588 introduces a new bootstrap strategy for the TestContext framework. Thus as of Spring Framework 4.1, a TestContextBootstrapper will assume the responsibility for determining what ContextLoader to use as the default. Consequently, previous support for supplying the class name for a custom, default ContextLoader will no longer be applicable.

Deliverables

Officially deprecate support for custom, default ContextLoader class names in the 4.0.x line for the following:

1. The TestContextManager(Class, String) constructor
2. The getDefaultContextLoaderClassName(Class) method in SpringJUnit4ClassRunner

---

Affects: 4.0 GA

Issue Links:

• Introduce bootstrap strategy in the TestContext framework [SPR-9955] #14588 Introduce bootstrap strategy in the TestContext framework ("is depended on by")
• Deprecate TestContextManager.getDefaultTestExecutionListenerClasses() [SPR-11679] #16302 Deprecate TestContextManager.getDefaultTestExecutionListenerClasses()

[spring-projects-issues]

Sam Brannen commented

Completed as described in the comments for GitHub commit d5ce30f:

Deprecate custom/default CtxLdr class name in TCF

Once the new bootstrap strategy for the TestContext framework (TCF) is
introduced in Spring Framework 4.1, a TestContextBootstrapper will
assume full responsibility for determining what ContextLoader to use as
the default. Consequently, the previous support for supplying the class
name for a custom, default ContextLoader will no longer be applicable.

This commit therefore officially deprecates support for custom, default
ContextLoader class names via the following mechanisms:

• The TestContextManager(Class, String) constructor

• The getDefaultContextLoaderClassName(Class) method in
  SpringJUnit4ClassRunner