Migrating to Spring Framework 3.2
- In this appendix we discuss discuss what users will want to know when upgrading to
+ In this appendix we discuss what users will want to know when upgrading to
Spring Framework 3.2. For a general overview of features, please see
@@ -124,6 +124,25 @@
for details.
+
+ Spring Test Dependencies
+
+ The spring-test module has been upgraded to
+ depend on JUnit 4.11 (junit:junit), TestNG 6.5.2
+ (org.testng:testng), and Hamcrest Core 1.3
+ (org.hamcrest:hamcrest-core). Each of these
+ dependencies is declared as an optional dependency
+ in the Maven POM. Furthermore, it is important to note that the JUnit
+ team has stopped inlining Hamcrest Core within the
+ junit:junit Maven artifact as of JUnit 4.11. Thus, if
+ your existing JUnit-based tests make use of Hamcrest matchers that were
+ previously available directly within the junit:junit
+ JAR, you will now need to explicitly declare a dependency on
+ org.hamcrest:hamcrest-core,
+ org.hamcrest:hamcrest-library, or
+ org.hamcrest:hamcrest-all.
+
+
Public API changes
@@ -265,20 +284,23 @@
- org.springframework.test.context.junit4.AbstractTransactionalJUnit4SpringContextTests
-
+ org.springframework.test.context.junit4.AbstractTransactionalJUnit4SpringContextTests:
+ use of the simpleJdbcTemplate instance variable has been deprecated
+ in favor of the new jdbcTemplate instance variable.
- org.springframework.test.context.testng.AbstractTransactionalTestNGSpringContextTests
-
+ org.springframework.test.context.testng.AbstractTransactionalTestNGSpringContextTests:
+ use of the simpleJdbcTemplate instance variable has been deprecated
+ in favor of the new jdbcTemplate instance variable.
- org.springframework.test.jdbc.SimpleJdbcTestUtils
-
+ org.springframework.test.jdbc.SimpleJdbcTestUtils has been deprecated in
+ favor of JdbcTestUtils which now contains all of the
+ functionality previously available in SimpleJdbcTestUtils.