Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 17 Nov 2011 18:55:51 +0000 (UTC)
From: "Alejandro Abdelnur (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <417092163.39683.1321556151145.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <156300933.36085.1321474915166.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3415) improve MiniMRYarnCluster &
 DistributedShell JAR resolution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Abdelnur updated MAPREDUCE-3415:
------------------------------------------

    Attachment: MAPREDUCE-3415.patch

as per Ahmed suggestion, not using temp dir anymore, instead using a dir within 'target', thus no need to do an explicit clean up.

Had to tweak the MiniMRClusterFactory to use JarFinder as it was not working when running test cases from root level because in that case there is no JAR for for the caller class. Also, this enables running the testcases from within IDEs (for the very same reason)
                
> improve MiniMRYarnCluster & DistributedShell JAR resolution 
> ------------------------------------------------------------
>
>                 Key: MAPREDUCE-3415
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3415
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.24.0, 0.23.1
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.24.0, 0.23.1
>
>         Attachments: MAPREDUCE-3415.patch, MAPREDUCE-3415.patch, MAPREDUCE-3415.patch, MAPREDUCE-3415.patch
>
>
> Current JAR resolution assumes the following:
> # The class used for JAR lookup is effectively in a JAR
> # A System property is set for testing with the location of the JAR
> The problem with #1 is that in some cases (when using the class in the same Maven module where the class is, the class is not in a JAR but in a directory 'target/test-classes').
> The problem with #2 is the JAR does not exists at the time of running the test (packaging comes after test and we are not doing integration testing yet thus won't work)
> In addition, this is required for streaming testcases, to have the JAR with streaming classes for testing.

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