You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2016/07/26 15:51:20 UTC
[jira] [Updated] (YETUS-435) hadoop: always build a custom
leveldbjni
[ https://issues.apache.org/jira/browse/YETUS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated YETUS-435:
-----------------------------------
Description: Apache Hadoop needs a shared library that is normally embedded in a dependency's jar file. This breaks all but three platforms. Response from Hadoop community has been that it is the user's responsibility to provide a working jar. Therefore, we need to fix this in the Yetus personality so that ppc64le builds in the Docker container work properly when custom maven repos are used. (was: Apache Hadoop needs a native library that is normally embedded in a dependency's jar file. This breaks all but three platforms. Response from Hadoop community has been that it is the user's responsibility to provide a working jar. Therefore, we need to fix this in the Yetus personality so that ppc64le builds in the Docker container work properly when custom maven repos are used.)
> hadoop: always build a custom leveldbjni
> ----------------------------------------
>
> Key: YETUS-435
> URL: https://issues.apache.org/jira/browse/YETUS-435
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
>
> Apache Hadoop needs a shared library that is normally embedded in a dependency's jar file. This breaks all but three platforms. Response from Hadoop community has been that it is the user's responsibility to provide a working jar. Therefore, we need to fix this in the Yetus personality so that ppc64le builds in the Docker container work properly when custom maven repos are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)