You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2022/01/17 12:11:00 UTC

[jira] [Commented] (ARROW-14336) [C++] Maintain bundled dependency tarballs in an Apache-managed location

    [ https://issues.apache.org/jira/browse/ARROW-14336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477158#comment-17477158 ] 

Krisztian Szucs commented on ARROW-14336:
-----------------------------------------

Uploaded the dependencies manually to artifactory https://apache.jfrog.io/ui/native/arrow/thirdparty

> [C++] Maintain bundled dependency tarballs in an Apache-managed location
> ------------------------------------------------------------------------
>
>                 Key: ARROW-14336
>                 URL: https://issues.apache.org/jira/browse/ARROW-14336
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Ian Cook
>            Assignee: Balazs Jeszenszky
>            Priority: Major
>             Fix For: 7.0.0
>
>
> The CMake scripts for the Arrow C++ library download bundled third-party dependencies from [https://github.com/ursa-labs/thirdparty/releases/]. Consider maintaining these in an ASF-managed location (probably http://apache.jfrog.io) instead of an Ursa Labs / Voltron Data-managed location. This would make it possible for Arrow committers / PMC members outside of Ursa / Voltron to upload new versions of these dependency tarballs (like in ARROW-14229).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)