[
https://issues.apache.org/jira/browse/PHOENIX-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275538#comment-17275538
]
ASF GitHub Bot commented on PHOENIX-6349:
-----------------------------------------
stoty commented on pull request #1123:
URL: https://github.com/apache/phoenix/pull/1123#issuecomment-770178977
I found the problem.
I've forgot to add the fixed phoenix-server pom.xml to the amended commit.
At least now I've run and end-to-end test on 5.x
Can you try yet again on 4.x with the now-really-fixed-i-swear patch
@yanxinyi ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add and use commons-cli to phoenix-thirdparty
> ---------------------------------------------
>
> Key: PHOENIX-6349
> URL: https://issues.apache.org/jira/browse/PHOENIX-6349
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.1.0, 4.16.0, thirdparty-1.1.0
>
>
> We are hit hard by commons-cli bugs, and currently we msut stick to the
> version used by HBase/Hadoop.
> Adding commons-cli to phoenix-thirdparty would unchain us from the
> Hbase/Hadoop version, and would let us add our own patches (modeled after
> protobuf in HBase)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
