You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Mingliang Liu (JIRA)" <ji...@apache.org> on 2017/02/24 23:59:44 UTC
[jira] [Resolved] (HADOOP-13994) explicitly declare the
commons-lang3 dependency as 3.4
[ https://issues.apache.org/jira/browse/HADOOP-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu resolved HADOOP-13994.
------------------------------------
Resolution: Fixed
> explicitly declare the commons-lang3 dependency as 3.4
> ------------------------------------------------------
>
> Key: HADOOP-13994
> URL: https://issues.apache.org/jira/browse/HADOOP-13994
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, fs/azure, fs/s3
> Affects Versions: 3.0.0-alpha2, HADOOP-13345
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: HADOOP-13345
>
> Attachments: HADOOP-13994-HADOOP-13345-001.patch, HADOOP-13994-HADOOP-13445-001.patch
>
>
> Other people aren't seeing this (yet?), but unless you explicitly exclude v 3.4 of commons-lang3 from the azure build (which HADOOP-13660 does), then the dependency declaration of commons-lang3 v 3.3.2 is creating a resolution conflict. That's a dependency only needed for the local dynamodb & tests.
> I propose to fix this in s3guard by explicitly declaring the version used in the tests to be that of the azure-storage one, excluding that you get for free. It doesn't impact anything shipped in production, but puts the hadoop build in control of what versions of commons-lang are coming in everywhere by way of the commons-config version declared in hadoop-common
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org