[
https://issues.apache.org/jira/browse/ATLAS-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150195#comment-16150195
]
Graham Wallis commented on ATLAS-2101:
--------------------------------------
Just a thought - why was this a problem with IntelliJ specifically? The earlier
problems I had seen with StopWatch occurred regardless of whether running in an
IDE or standalone (from command line).
Is there a possibility that IntelliJ was picking up the wrong Guava due to
module classpath settings?
> 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)
