[
https://issues.apache.org/jira/browse/MAPREDUCE-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412381#comment-13412381
]
Kihwal Lee commented on MAPREDUCE-4416:
---------------------------------------
Patrick, thanks for the comment. That might work, but the fact that it's not
really an app-level dependency bothers me. So I ended up adding the dependency
inside the clover profile in hadoop-project/pom.xml. This causes each module to
have clover jar as a dependency when -Pclover is specified. All
mrapp-generated-classpath files will include the path to the clover jar. The
package build will copy and include the clover jar, but we can't really use
instrumented packages anyway.
As an alternative to globally adding the dependency, we can do it per module
whenever necessary. At least the following two needs the dependency specified.
- hadoop-yarn-applications
- hadoop-mapreduce-client-jobclient
> Some tests fail if Clover is enabled
> ------------------------------------
>
> Key: MAPREDUCE-4416
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4416
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Kihwal Lee
> Priority: Critical
> Fix For: 2.0.1-alpha, 3.0.0
>
>
> There are number of tests running under hadoop-mapreduce-client-jobclient
> that fail if Clover is enabled. Whenever a job is launched, AM doesn't start
> because it can't locate the clover jar file.
> I thought MAPREDUCE-4253 had something to do this, but I can reproduce the
> issue on an older revision. Although unrelated, MAPREDUCE-4253 does have a
> problem and it has been reported to the jira.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
