hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-13541) explicitly declare the Joda time version S3A depends on
Date Wed, 24 Aug 2016 13:53:20 GMT
Steve Loughran created HADOOP-13541:
---------------------------------------

             Summary: 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


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


Mime
View raw message