You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2013/07/16 09:56:49 UTC
[jira] [Updated] (HADOOP-9737) JarFinder#getJar should delete the
jar file upon destruction of the JVM
[ https://issues.apache.org/jira/browse/HADOOP-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Esteban Gutierrez updated HADOOP-9737:
--------------------------------------
Description:
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}}
was:
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}}
> 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