[
https://issues.apache.org/jira/browse/PHOENIX-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262430#comment-17262430
]
ASF GitHub Bot commented on PHOENIX-6309:
-----------------------------------------
stoty commented on pull request #1082:
URL: https://github.com/apache/phoenix/pull/1082#issuecomment-757658696
In that it probably not a regression, I just never got around to backporting
that cleanup to 4.x
I'll leave it to your discretion wheter you want to that for ticket.
----------------------------------------------------------------
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]
> Use maven enforcer to ban imports
> ---------------------------------
>
> Key: PHOENIX-6309
> URL: https://issues.apache.org/jira/browse/PHOENIX-6309
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> We are already using mvn enforcer plugin for hbase version evaluations. We
> can extend it's usage to restrict-imports-enforcer-rule enforcer and ban
> imports from illegal packages (as per our project guidelines)
> e.g restrict usage of org.apache.commons.logging, com.google.common (in the
> presence of phoenix-thirdparty in Phoenix 5.x) etc.
> While doing backports from 4.x to master and vice-versa, it's quite common
> for these branch specific imports rules to get ignored by devs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
