[CASSANDRA-16379] do not use http maven repo defined by MAT

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Component/s: Packaging
• Bug Category: Packaging - All
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Assignee: Unassigned
• Reporter: Brandon Williams
• Created: 11/Jan/21 15:31
• Updated: 02/Apr/21 08:59
• Resolved: 02/Apr/21 08:59

Description

We have had strange, somewhat inexplicable issues during building with pulling from maven central via HTTP, which fails as HTTPS is now required. We last hacked around this in acf8de28ce2f2871e30e4a55086a38d850470f3e, but it was just that, a hack.

The crux of the problem seems to come from MAT, according to https://stackoverflow.com/questions/59948747/maven-ant-task-transitive-pom-dependencies-and-https-issue

Indeed, in our build.xml here: https://github.com/apache/cassandra/blob/trunk/build.xml#L481 we are using the central definition it provides. I propose instead overriding this definition to "https://repo1.maven.org/maven2/" which fixes the build in every case I've tried during a bisect.

Issue Links

• duplicates: CASSANDRA-16391 Migrate dependency handling from maven-ant-tasks to resolver-ant-tasks
• relates to: CASSANDRA-16359 mvn-install fails if no repo mirror is defined in settings.xml