The JUnit team recently released JUnit 4.11.
The following information is applicable to the Spring Framework build, especially with regard to junit:junit vs. junit:junit-dep and Hamcrest Maven dependencies.
Up until now there were two Maven artifacts for JUnit: junit:junit-dep and junit:junit. From a Maven point-of-view only the former made sense because it did not contain the Hamcrest classes but declared a dependency to the Hamcrest Maven artifact. The latter included the Hamcrest classes which was very un-Maven-like.
From this release on, you should use junit:junit which will be what junit:junit-dep used to. If you still reference junit:junit-dep, Maven will automatically relocate you to the new junit:junit and issue a warning for you to fix.
- Upgrade the dependency on JUnit in the spring-test module from 4.10 to 4.11.
- Update the entire Gradle build to use JUnit 4.11 instead of the 4.11 snapshot build currently in use.
- Update the changelog.