yetus-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <>
Subject [jira] [Commented] (YETUS-435) hadoop: always build a custom leveldbjni
Date Tue, 16 Aug 2016 16:30:20 GMT


Allen Wittenauer commented on YETUS-435:

It's a bit more complex than that.

Currently, people are working around this by building leveldbjni via mvn install outside of
the build process.  This causes the bits to get installed into the ~/.m2 repo so that when
Hadoop builds, it picks it up from there.

In the case of Yetus, we can't do that because when we pass --mvn-custom-repos to change from
~/.m2 to a different location (to avoid the maven cache collision problem), we won't have
leveldbjni in it. So we have to build leveldbjni during the Yetus run, not before.

 There's also the question around consistency.  Yetus should probably do this for *all* platforms,
including the three that leveldbjni-all actually includes.

> hadoop: always build a custom leveldbjni
> ----------------------------------------
>                 Key: YETUS-435
>                 URL:
>             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

View raw message