[
https://issues.apache.org/jira/browse/YETUS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394193#comment-15394193
]
Chris Nauroth commented on YETUS-435:
-------------------------------------
[~aw], thank you for the notice.
I'm a little unclear about the proposed solution. Reading this the first time,
I thought the intent was for test-patch to pull the LevelDB source and
compile/link for PowerPC each time. However, then I also saw mention of
working with a custom Maven repo in the description. Does that mean this would
be a one-time push of a LevelDB build for PowerPC to a custom Maven repo, and
then all subsequent test-patch runs would pull it from that repo?
> 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 four 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
> ASF Jenkins 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)
