[
https://issues.apache.org/jira/browse/IMPALA-11667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629218#comment-17629218
]
ASF subversion and git services commented on IMPALA-11667:
----------------------------------------------------------
Commit 543399c4715eb1f555bece691b63541630415198 in impala's branch
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=543399c47 ]
IMPALA-11667: (Addendum) Remove explicit include of spring-core
Removes the specific exclude of spring-core from pac4j in favor of
setting versions in dependencyManagement. Continues to exclude other
springframework libraries (spring-orm from opensaml-storage-impl).
Change-Id: Ifc9b46b45ed24e5e924db88ef792c1a68a906394
Reviewed-on: http://gerrit.cloudera.org:8080/19153
Reviewed-by: Joe McDonnell <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Clean up POMs using dependencyManagement
> ----------------------------------------
>
> Key: IMPALA-11667
> URL: https://issues.apache.org/jira/browse/IMPALA-11667
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Affects Versions: Impala 4.1.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Critical
> Fix For: Impala 4.2.0
>
>
> Conflicts in Impala's Java transitive dependencies have historically been
> handled by excluding them from immediate dependencies and directly including
> the conflicted package. This requires monitoring for that package in any new
> dependencies and carrying exclusions across a number of packages.
> Maven provides a depedencyManagement section to directly control versions of
> transitive dependencies. Use this to clean up many of Impala's exclusions so
> they're easier to maintain.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
