[
https://issues.apache.org/jira/browse/HADOOP-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123142#comment-14123142
]
Tsuyoshi OZAWA commented on HADOOP-11032:
-----------------------------------------
[~gsteelman], thanks for your suggestions.
{quote}
Any idea if the build scripts changed and that's the reason we can't find
SpanReceiverHost?
{quote}
I think HDFS-7001 is addressing the problem.
{quote}
Second, I think a silent pass or a Log.warn() statement would suffice for
StopWatch.stop() twice in a row.
{quote}
Do you mean should we add wrapper class of Stopwatch to handle them? It also
can be overkill. I think we should it's enough to use Stopwatch class correctly.
{quote}
And finally, if we remove the patch 3 attachment and re-upload it as patch 3
again, will Jenkins will build with patch 3 again?
{quote}
Yes, Jenkins will :-)
> Replace use of Guava Stopwatch with Apache StopWatch
> ----------------------------------------------------
>
> Key: HADOOP-11032
> URL: https://issues.apache.org/jira/browse/HADOOP-11032
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Gary Steelman
> Assignee: Tsuyoshi OZAWA
> Attachments: HADOOP-11032.1.patch, HADOOP-11032.2.patch,
> HADOOP-11032.3.patch
>
>
> This patch reduces Hadoop's dependency on an old version of guava.
> Stopwatch.elapsedMillis() isn't part of guava past v16 and the tools I'm
> working on use v17.
> To remedy this and also reduce Hadoop's reliance on old versions of guava, we
> can use the Apache StopWatch (org.apache.commons.lang.time.StopWatch) which
> provides nearly equivalent functionality. apache.commons.lang is already a
> dependency for Hadoop so this will not introduce new dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
