You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/08/24 14:36:20 UTC
[jira] [Updated] (HADOOP-13541) explicitly declare the Joda time
version S3A depends on
[ https://issues.apache.org/jira/browse/HADOOP-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13541:
------------------------------------
Attachment: HADOOP-13541-branch-2.8-001.patch
Patch against branch-2.8; it's the first one lagging the 2.7.3 version.
we should also consider applying this to branch-2.7, to retain version control there in the face of any upgrade of dependencies
> explicitly declare the Joda time version S3A depends on
> -------------------------------------------------------
>
> Key: HADOOP-13541
> URL: https://issues.apache.org/jira/browse/HADOOP-13541
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build, fs/s3
> Affects Versions: 2.8.0, 2.7.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-13541-branch-2.8-001.patch
>
>
> Different builds of Hadoop are pulling in wildly different versions of Joda time, depending on what other transitive dependencies are involved. Example: 2.7.3 is somehow picking up Joda time 2.9.4; branch-2.8 is actually behind on 2.8.1. That's going to cause confusion when people upgrade from 2.7.x to 2.8 and find a dependency has got older
> I propose explicitly declaring a dependency on joda-time in s3a, then set the version to 2.9.4; upgrades are things we can manage
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org