[
https://issues.apache.org/jira/browse/HADOOP-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639505#comment-13639505
]
Chris Nauroth commented on HADOOP-9290:
---------------------------------------
{quote}
The simplest solution which just works is to add duplicate entries in the path
for different levels of nesting (2-4 should do the trick I think).
{quote}
I'd be +1 for that approach. I suppose the only potential risk is that modules
at a lower nesting level could accidentally load a library from outside the
entire project root, but it seems highly unlikely that the full path would
exist outside the project and happen to have a libhadoop.so or hadoop.dll
inside it. It probably won't happen in practice.
BTW, the reason I've come back to this jira is that it came up in discussion on
HADOOP-9413. That patch would cause some test failures unless we also solve
HADOOP-9290.
> Some tests cannot load native library
> -------------------------------------
>
> Key: HADOOP-9290
> URL: https://issues.apache.org/jira/browse/HADOOP-9290
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, native
> Affects Versions: 3.0.0, trunk-win
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HADOOP-9290.patch
>
>
> Some tests are unable to load the native DLL on Windows. The culprit appears
> to be an incorrect PATH configuration for the native-win profile in
> hadoop-project/pom.xml.
> {code:xml}
> <profile>
> <id>native-win</id>
> <activation>
> <os>
> <family>Windows</family>
> </os>
> </activation>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <environmentVariables>
> <!-- Specify where to look for the native DLL on Windows -->
>
> <PATH>${env.PATH};${basedir}\..\..\hadoop-common-project\hadoop-common\target\bin;</PATH>
> </environmentVariables>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> {code}
> This is evaluated independently by each project and the relative path is not
> always correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
