[
https://issues.apache.org/jira/browse/HADOOP-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037428#comment-18037428
]
ASF GitHub Bot commented on HADOOP-19503:
-----------------------------------------
stoty commented on PR #8074:
URL: https://github.com/apache/hadoop/pull/8074#issuecomment-3516593140
> If some hadoop module says I depend on jackson-bom 2.18 and so we get 2.18
jackson-core that way, it is coming in transitively, one two levels down the
tree.
I don't think replacing the explicit dependency management entries with the
imported BOM has any effect on downstream projects. The BOM itself does not get
added as a parent of the jackson artifacts.
AFAIU importing the bom is equivalent to copying its dependencyManagement
entries the dependencyManagement section, the hadoop artifacts will still have
the same dependencies at the same level as before.
I have run dependency:tree on trunk and with this patch.
The only difference is that the transitive
**com.fasterxml.jackson.datatype:jackson-datatype-jsr310** and
**com.fasterxml.jackson.dataformat:jackson-dataformat-smile** dependencies were
previously not dependency managed, and with the patch they are.
> Use jackson-bom to set jackson versions
> ---------------------------------------
>
> Key: HADOOP-19503
> URL: https://issues.apache.org/jira/browse/HADOOP-19503
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Minor
> Labels: pull-request-available
>
> It is much easier to maintain than the current direct dependencyManagement
> entries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
