[
https://issues.apache.org/jira/browse/HADOOP-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-9290:
----------------------------------
Attachment: HADOOP-9290.4.patch
I'm uploading version 4 of the patch. I think this will be the final version
(pending review and +1 of course). I'm reusing hadoop.common.build.dir to
specify the path for both winutils.exe and the native libraries. You'll see
that the child pom.xml files need to override much less of the
maven-surefire-plugin configuration now, so there is less code to maintain.
Basically, the child pom.xml files are going back to the state of HADOOP-8755
(introduction of {{TimedOutTestsListener}}) + the small override of
hadoop.common.build.dir.
I successfully reran my tests from last time (multiple tests, running at
multiple nesting levels in the source tree, running on multiple platforms).
> 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.3.patch,
> HADOOP-9290.4.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
