[
https://issues.apache.org/jira/browse/CASSANDRA-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266900#comment-17266900
]
Michael Semb Wever commented on CASSANDRA-16379:
------------------------------------------------
To manually download all dependencies, which is a one-time workaround, the
following steps can be used
{code}
ant write-poms
mvn dependency:go-offline -f ./build/apache-cassandra-4.0-beta5-SNAPSHOT.pom
{code}
I've used a [similar
approach|https://issues.apache.org/jira/browse/CASSANDRA-16384?focusedCommentId=17266899&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17266899]
to check authenticity of updated jar files under {{lib/}}.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
