From ae0c34baaf341bd65a1077d472e3b161cce2e704 Mon Sep 17 00:00:00 2001 From: Sam Brannen Date: Fri, 1 Feb 2013 15:40:01 +0100 Subject: [PATCH] Improve 3.2 migration guide re: JUnit & Hamcrest This commit improves the "Spring Test Dependencies" section of the 3.2 migration guide by correctly explaining that Hamcrest Core is now a required transitive dependency of JUnit. Issue: SPR-10251 --- src/reference/docbook/migration-3.2.xml | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/src/reference/docbook/migration-3.2.xml b/src/reference/docbook/migration-3.2.xml index c96b43d8ba..79f5c9150c 100644 --- a/src/reference/docbook/migration-3.2.xml +++ b/src/reference/docbook/migration-3.2.xml @@ -138,16 +138,14 @@ 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. + 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. Hamcrest + Core is now a required transitive dependency of + junit, and users may therefore need to remove any + exclusions on hamcrest-core that they had previously + configured for their build.