Bug #3598: Not specifying maven default repos lead to inconsistency in download - Rudder - Issue Tracker

Actions

Copy link

Bug #3598

closed

Not specifying maven default repos lead to inconsistency in download

Added by François ARMAND over 11 years ago. Updated over 11 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

Architecture - Dependencies

Target version:

2.3.13

Pull Request:

https://github.com/Normation/rudder-p...

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.

Related issues 1 (0 open — 1 closed)