hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13541) explicitly declare the Joda time version S3A depends on
Date Fri, 02 Sep 2016 18:45:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459272#comment-15459272

Andrew Wang commented on HADOOP-13541:

I'll +1 on faith, I assume you ran mvn dependency plugin to verify.

Any thoughts about how we can prevent/verify this kind of thing for the future? I don't think
it's picked up by our API checking tool.

> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message