[
https://issues.apache.org/jira/browse/HADOOP-9737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536472#comment-14536472
]
Hudson commented on HADOOP-9737:
--------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #922 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/922/])
HADOOP-9737. JarFinder#getJar should delete the jar file upon destruction of
the JVM (jbonofre via rkanter) (rkanter: rev
315074bb08e0f2c9508834ada62f1533ffd82a26)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/JarFinder.java
> 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: Improvement
> Components: util
> Affects Versions: 2.0.0-alpha
> Reporter: Esteban Gutierrez
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.8.0
>
> Attachments: HADOOP-9737.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
