I've just noticed a change in behaviour b/w maven 2.0.8 and 2.0.9 releases. In our project we had two dependencies of ehcache defined each a different version and unfortunately each using a different groupid in the artifact's pom.xml that referenced the dependency.
It seems if you build with v 2.0.9 you end up with different versions of ehcache being added to lib whereas in v 2.0.8 you would only have the most recent version of ehcache despite the dependency references differing by groupid. Does anybody remember anything specifically introduced in 2.0.9 that made the groupid significant when assessing the dependencies? Perhaps it's not groupid but what's what differed. 2.0.7, 2.0.8 result in one version of ehcache despite the references having differed by groupid where as 2.0.9 results in two versions of ehcache being identified.
