[
https://issues.apache.org/jira/browse/PHOENIX-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175356#comment-17175356
]
Istvan Toth edited comment on PHOENIX-6064 at 8/24/20, 7:20 AM:
----------------------------------------------------------------
[~larsh] Yes, it is a cop-out, as a quicker alternative to factoring out Twill
from Tephra.
However, as the default option is to build with Tephra, and omitting Tephra has
to be explicitly specified, I don't agree that it means dropping Tephra support.
It does diminish the incentive to bring Tephra to the standard of the rest of
the components wrt Phoenix-thirdparty.
was (Author: stoty):
[~larsh] Yes, it is a cop-out, as a quicker alternative to factoring out Twill
from Tephra.
However, as the default option is to build with Guava, and omitting Guava has
to be explicitly specified, I don't agree that it means dropping Tephra support.
It does diminish the incentive to bring Tephra to the standard of the rest of
the components wrt Phoenix-thirdparty.
> 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
> Attachments: PHOENIX-6064.master.v1.patch
>
> Time Spent: 10m
> 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.3.4#803005)
