Trying to upgrade Spring Data JPA from 3.1.2.RELEASE to 3.2.0.BUILD-SNAPSHOT broke my dependency setup as the test module apparently has hamcrest-all as hard dependency in a really ancient version (1.1 (2007), current is 1.3).
The reason this broke is that my project depends on hamcrest-library only, so that my local declaration of the 1.3 version does not get preferred. I fear we might break quite a few projects with that move as setting up JUnit and Hamcrest to work reasonably is quite a dance anyway and it's not really obvious why tests suddenly don't compile anymore.
Can we make Hamcrest an optional dependency?
If not, do we really need the broad hamcrest-all or is hamcrest-library enough as it contains all the Matcher implementations (see http://code.google.com/p/hamcrest/wiki/HamcrestDistributables for details).
If not, could we at least refer to the latest version (1.3).