[HADOOP-13994] explicitly declare the commons-lang3 dependency as 3.4

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2, HADOOP-13345
• Fix Version/s: HADOOP-13345
• Component/s: build, fs/azure, fs/s3
• Target Version/s: HADOOP-13345
• Hadoop Flags: Reviewed
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 17/Jan/17 20:56
• Updated: 24/Feb/17 23:59
• Resolved: 24/Feb/17 23:59

Description

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

Issue Links

• is depended upon by: HADOOP-9991 Fix up Hadoop POMs, roll up JARs to latest versions
• is related to: HADOOP-13660 Upgrade commons-configuration version to 2.1