[ https://issues.apache.org/jira/browse/HADOOP-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470367#comment-15470367 ]
Hudson commented on HADOOP-13541: --------------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10404 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10404/]) HADOOP-13541 explicitly declare the Joda time version S3A depends on. (stevel: rev 7fdfcd8a6c9e2dd9b0fb6d4196bc371f6f9a676c) * (edit) hadoop-project/pom.xml * (edit) hadoop-tools/hadoop-aws/pom.xml > 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 > Fix For: 2.8.0 > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org