[
https://issues.apache.org/jira/browse/HADOOP-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640105#comment-13640105
]
Arpit Agarwal commented on HADOOP-9290:
---------------------------------------
Chris,
I verified MR tests that could not load hadoop.dll can do so now after the fix.
e.g. TestJobImpl.
Would you consider adding a one-line comment to hadoop-project/pom.xml
explaining why the definition of hadoop.common.build.dir has the /../../? And
the fact that it must be overridden for projects with different levels of
nesting.
{code}
+
<hadoop.common.build.dir>${basedir}/../../hadoop-common-project/hadoop-common/target</hadoop.common.build.dir>
{code}
+1 otherwise. There is no clean way to fix it and this approach is the best
option I can think of.
> 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
> Reporter: Arpit Agarwal
> Assignee: Chris Nauroth
> Attachments: HADOOP-9290.2.patch, 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
