[
https://issues.apache.org/jira/browse/PHOENIX-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-5635:
---------------------------------
Description:
The way we currently override the Omid curator version by excluding it from
omid, and directly depending on is needlessly complex.
It is much more straightforward to use dependencyManagement for this purpose.
Also there a few places in the code that refer to the shaded guava List class
in curator, instead of directly to guava for no discernible reason (probably
IDE automation chose the curator class)
was:
The way we currently override the Omid curator version by excluding it from
omid, and directly depending on is not needlessly complex.
It is much more straightforward to use dependencyManagement for this purpose.
Also there a few places in the code that refer to the List class in curator,
instead of the guava one for no discernible reason (probably IDE automation
chose the curator class)
> Refactor curator dependency handling and clean up erroneous direct references
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-5635
> URL: https://issues.apache.org/jira/browse/PHOENIX-5635
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Minor
> Attachments: PHOENIX-5635.master.v1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The way we currently override the Omid curator version by excluding it from
> omid, and directly depending on is needlessly complex.
> It is much more straightforward to use dependencyManagement for this purpose.
> Also there a few places in the code that refer to the shaded guava List class
> in curator, instead of directly to guava for no discernible reason (probably
> IDE automation chose the curator class)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
