[
https://issues.apache.org/jira/browse/HADOOP-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260510#comment-15260510
]
Hudson commented on HADOOP-5470:
--------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9683 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9683/])
HADOOP-5470. RunJar.unJar() should write the last modified time found in (arp:
rev 3337ef2bfecb63f7f238ab72bbde62a0bbb4288d)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/RunJar.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/TestRunJar.java
> RunJar.unJar() should write the last modified time found in the jar entry to
> the uncompressed file
> --------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5470
> URL: https://issues.apache.org/jira/browse/HADOOP-5470
> Project: Hadoop Common
> Issue Type: Improvement
> Components: util
> Affects Versions: 2.7.2
> Reporter: Colin Evans
> Assignee: Andras Bokor
> Priority: Minor
> Labels: newbie
> Fix For: 2.8.0
>
> Attachments: HADOOP-5470.01.patch, HADOOP-5470.02.patch,
> HADOOP-5470.03.patch, HADOOP-5470.04.patch, HADOOP-5470.05.patch,
> HADOOP-5470.06.patch
>
>
> For tools like jruby and jython, last modified times determine if a script
> gets recompiled. Losing the correct last modified time causes some
> unfortunate recompilation race conditions when a job is running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
