[
https://issues.apache.org/jira/browse/PHOENIX-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781361#comment-17781361
]
ASF GitHub Bot commented on PHOENIX-7091:
-----------------------------------------
NihalJain opened a new pull request, #140:
URL: https://github.com/apache/phoenix-queryserver/pull/140
…y-server
- Add maven-enforcer-plugin and use it to ban commons-logging and other
logging framework related jars
- Remove all traces of log4j:log4j, org.slf4j:slf4j-log4j12 and
commons-logging:commons-logging from dependency list
- Replace log4j.properties with log4j2.properties (copied from hbase project)
- Fix issue where IT logs where not getting logged in surefire reports due
to "Failed to load class "org.slf4j.impl.StaticLoggerBinder"
- See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
- Fix log4j duplicate dependency warning in pom.xml
> Cleanup and ban log4j and related jars from phoenix-query-server
> ----------------------------------------------------------------
>
> Key: PHOENIX-7091
> URL: https://issues.apache.org/jira/browse/PHOENIX-7091
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
>
> PQS has moved to log4j2 in
> [PHOENIX-6931|https://github.com/apache/phoenix-queryserver/pull/130] but
> there are still traces of log4j:log4j in the build. This task is to delete
> all traces of log4j from build and also explicitly ban them from coming back
> again in future via maven-enforcer-plugin
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
