[
https://issues.apache.org/jira/browse/PHOENIX-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265680#comment-17265680
]
ASF GitHub Bot commented on PHOENIX-6307:
-----------------------------------------
stoty commented on pull request #1086:
URL: https://github.com/apache/phoenix/pull/1086#issuecomment-760637636
Thank you @yanxinyi.
The big issue here is not the maven mechanical changes, but new
artifact/file naming scheme, and you and @joshelser have already approved that
on the list.
Having approval from both sides is enough for me.
----------------------------------------------------------------
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]
> Build and release official binary distributions with each HBase profile
> -----------------------------------------------------------------------
>
> Key: PHOENIX-6307
> URL: https://issues.apache.org/jira/browse/PHOENIX-6307
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Affects Versions: 5.1.0, 4.16.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Attachments: PHOENIX-6307-docs.patch
>
>
> The release scripts curently assume that we release a single binary artifact
> for Phoenix.
> Change the release scripts, so that binaries are built ans released for each
> HBase profile.
> Also revert the change that omits the phoenix-compatibility classes from
> phoenix-server, as it not needed, and a potentical source of problems with
> this approach.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
