You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2021/04/02 09:00:01 UTC

[jira] [Updated] (CASSANDRA-16379) do not use http maven repo defined by MAT

     [ https://issues.apache.org/jira/browse/CASSANDRA-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Semb Wever updated CASSANDRA-16379:
-------------------------------------------
    Resolution: Duplicate
        Status: Resolved  (was: Open)

> do not use http maven repo defined by MAT
> -----------------------------------------
>
>                 Key: CASSANDRA-16379
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16379
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>            Reporter: Brandon Williams
>            Priority: Normal
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org