Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0.2, 1.1-beta-2
-
Fix Version/s: 1.1-beta-3
-
Component/s: core
-
Labels:None
-
Environment:all
-
Number of attachments :
Description
Maven should check downloaded artifacts for integrety, especially .jar files, since they can get corrupted by e.g. bad cvswrappers (no -kb) and other things. Right now there is no way to now if a .jar is containing all information once the filename exists in the local repository
/peter
Issue Links
| This issue is duplicated by: | ||||
| MAVEN-430 | maven checks md5 checksums at wrong point. |
|
|
|
| This issue is related to: | ||||
| MAVEN-1648 | Maven 1.1-beta-1 no longer downloads MD5 sums to local repository |
|
|
|
| MAVEN-1080 | Maven download corrupted jar file into repository |
|
|
|
| This issue depends upon: | ||||
| MAVEN-1080 | Maven download corrupted jar file into repository |
|
|
|
+1 for resolving this issue. I'am unhappy user of very slow and bad connection and sometimes downloading of artifacts fails. After I retry executing the goal Maven doesn't reget partial missing file but it treats the broken jar as valid. The task execution fails.
I suggest downloading artifacts to temporary directory instead of repository dir and check the md5 sum before copying the jar to it's destination location in local repository. It will be safer and should eliminate the problems with repository integrity.