Recently dependencies were updated to newer versions but enforcer still checks
the old versions.
I've anticipated this happening. This is why I requested in the design phase of
our checking to be able to leave out the version number so that it always
checks the same version being used in the dependency mechanism.
Ultimately, I think this kind of checking needs to go into Maven itself, so you
can specifiy checksums in the <dependencies> section.
Original issue reported on code.google.com by andreas....@gmail.com on 26 Sep 2013 at 11:54
Original issue reported on code.google.com by
andreas....@gmail.com
on 26 Sep 2013 at 11:54