[
https://issues.apache.org/jira/browse/PHOENIX-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463007#comment-17463007
]
Lars Hofhansl commented on PHOENIX-6064:
----------------------------------------
Turns out this actually break Tephra completely and nobody even noticed.
Not blaming this change, but Phoenix and associated projects have started to
bitrot it seems.
Anyway... I don't work on this more, was just trying something unrelated. Which
then turned in a few hours getting Tephra to build without no longer supported
JDKs following by the realization that Phoenix cannot even load the
TephraTransactionProvider anymore.
Not sure why I even care - and if this sounds frustrated is because I am.
> Make Tephra support optional
> ----------------------------
>
> Key: PHOENIX-6064
> URL: https://issues.apache.org/jira/browse/PHOENIX-6064
> Project: Phoenix
> Issue Type: Improvement
> Components: core, tephra
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.1.0
>
> Attachments: PHOENIX-6064.master.v1.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Tephra has and old Guava dependency, that cannot be removed due to Twill
> depending on it. Removing the Twill dependency from Tephra is possible, but
> not trivial.
> This Guava has CVEs, which will show up in static analysis tools, which will
> cause some potential users not to adopt Phoenix.
> Provide an option to build Phoenix without Tephra, and its problematic
> dependencies.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
