hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4644) mapreduce-client-jobclient-tests do not run from dist tarball
Date Thu, 13 Sep 2012 21:51:08 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455345#comment-13455345
] 

Jason Lowe commented on MAPREDUCE-4644:
---------------------------------------

Agreed it's risky to blindly pull in all test scope JARs, so maybe it needs to be an explicit
list of jars to include.

bq. are you suggesting to create a new libtest/ dir? Wouldn't make more sense to have a tools
module for this? this seems like a tool usecase.

I'm not sure it's best to clutter the tools directory with the unit test jars. They're not
really related, and it can lead to some of the same problems we're trying to avoid when someone
runs tools.  IMHO the test stuff shouldn't be in the classpath unless you're running tests,
and tools aren't tests.

So yes, I'm proposing a separate place to store the tests and their dependencies.  This implies
the user needs to modify the classpath to run the tests, and we could make this easier by
providing a "hadoop tests-classpath" tool or something similar to aid them in doing so.
                
> mapreduce-client-jobclient-tests do not run from dist tarball
> -------------------------------------------------------------
>
>                 Key: MAPREDUCE-4644
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4644
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: build, test
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Priority: Blocker
>
> The mapreduce jobclient tests rely on junit which is missing from the dist tarball. 
This prevents running often-used tests like sleep jobs.

--
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

Mime
View raw message