Actions
Bug #3598
closed
Not specifying maven default repos lead to inconsistency in download
Status:
Released
Priority:
1
Assignee:
Category:
Architecture - Dependencies
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Maven seems to use it's central repo (http://repo1.maven.org/maven2/) as a fallback after having tryed other specified repos. That's stupid, it should be the other way around (use maven central, and if not found, use other repos).
That is not only an annoyance, it causes error for some plugin that are corrupted and download from a bad repos:
Downloading: http://repos.zeroturnaround.com/maven2/org/apache/maven/wagon/wagon-ssh/1.0-beta-6/wagon-ssh-1.0-beta-6.pom [WARNING] Checksum validation failed, expected <!DOCTYPE but is 9221655339dcee6f43095763b639c82c8e710699 for http://repos.zeroturnaround.com/maven2/org/apache/maven/wagon/wagon-ssh/1.0-beta-6/wagon-ssh-1.0-beta-6.pom [WARNING] Checksum validation failed, expected <!DOCTYPE but is 9221655339dcee6f43095763b639c82c8e710699 for http://repos.zeroturnaround.com/maven2/org/apache/maven/wagon/wagon-ssh/1.0-beta-6/wagon-ssh-1.0-beta-6.pom ....
And that lead to error further in the build process.
So, we have to specify central maven repos.
Updated by François ARMAND almost 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-parent-pom/pull/8
Updated by François ARMAND almost 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset parent-pom:commit:b8097c1425c7d9aedd4886b18fc6950edd6cf38f.
Updated by Nicolas CHARLES almost 11 years ago
Applied in changeset parent-pom:commit:31d3e006cbf4e8a8bb4fff599005e44409004c8b.
Updated by Nicolas PERRON almost 11 years ago
- Status changed from Pending release to Released
Actions