Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 16 Jul 2013 15:06:49 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12657941.1373961314262.58291.1373987209681@arcas>
In-Reply-To: <JIRA.12657941.1373961314262@arcas>
References: <JIRA.12657941.1373961314262@arcas>
Subject: [jira] [Commented] (HADOOP-9737) JarFinder#getJar should delete the
 jar file upon destruction of the JVM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on HADOOP-9737:
--------------------------------------------

agree with Harsh, no need for a config. Also, keep in mind JarFinder is a Hadoop test artifact, not part of Hadoop public API.
                
> JarFinder#getJar should delete the jar file upon destruction of the JVM
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-9737
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9737
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.0.0-alpha
>            Reporter: Esteban Gutierrez
>
> Once {{JarFinder.getJar()}} is invoked by a client app, it would be really useful to destroy the generated JAR after the JVM is destroyed by setting {{tempJar.deleteOnExit()}}. In order to preserve backwards compatibility a configuration setting could be implemented, e.g. {{test.build.dir.purge.on.exit}}

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