Currently, the maven-external-dependency-plugin is not overly smart about
picking the right checksum algorithm straight-away; it always tries MD5 first
and only if that fails does it try SHA1. Depending on the size of the external
dependency, computing the ckecksum may take a few seconds, which could be saved
if the plugin would apply the following heuristic:
40 hex digits => 160 bit SHA-1 checksum
otherwise => 128 bit MD5 checksum first, then 160 bit SHA-1 checksum
Alternatively, the plugin's goal would use two distinct parameters: md5checksum
and sha1checksum, probably with checksum retained for compatibility.
Original issue reported on code.google.com by s...@st.informatik.tu-darmstadt.de on 18 Apr 2012 at 8:37
Original issue reported on code.google.com by
s...@st.informatik.tu-darmstadt.de
on 18 Apr 2012 at 8:37