[
https://issues.apache.org/jira/browse/ATLAS-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148594#comment-16148594
]
Graham Wallis commented on ATLAS-2101:
--------------------------------------
Hi Ashutosh,
I have, in the past, seen problems caused by the change in Guava v17 from using
a public StopWatch constructor to a private constructor called by a factory
method. Some of the Atlas stack depends on the older style and I think my build
had picked up the wrong version of Guava, although I don't recall why.
I agree that if we possible we should remove the dependency altogether.
> Remove use of Guava Stopwatch from Atlas
> ----------------------------------------
>
> Key: ATLAS-2101
> URL: https://issues.apache.org/jira/browse/ATLAS-2101
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: trunk
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Minor
> Fix For: trunk
>
> Attachments: StandardIDPool.java
>
>
> *Background*
> Using _IntelliJ_ attempt to start Atlas server. Chances are the startup will
> fail due to error in resolving _com.google.common.base.StopWatch_.
> Similar problem is observed on some build environments.
> *Solution*
> * Add _StandardIDPool.java_ to shaded _Titan0_ JAR.
> * Replace use of _Stopwatch_ with some alternative implementation.
> See also: [HBASE-14963|https://issues.apache.org/jira/browse/HBASE-14963]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
