[
https://issues.apache.org/jira/browse/HADOOP-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874031#comment-17874031
]
ASF GitHub Bot commented on HADOOP-19153:
-----------------------------------------
steveloughran opened a new pull request, #6999:
URL: https://github.com/apache/hadoop/pull/6999
- Critical: remove the obsolete exclusion list from hadoop-common.
- Diligence: expand the hadoop-project exclusion list to exclude all
ch.qos.logback artifacts
### How was this patch tested?
* Manual inspection of the pom as installed in local maven repo
* hadoop-release-support maven verified that logback wasn't coming in
transitively
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> hadoop-common still exports logback as a transitive dependency
> --------------------------------------------------------------
>
> Key: HADOOP-19153
> URL: https://issues.apache.org/jira/browse/HADOOP-19153
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, common
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
>
> Even though HADOOP-19084 set out to stop it, somehow ZK's declaration of a
> logback dependency is still contaminating the hadoop-common dependency graph,
> so causing problems downstream.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
