hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10394) move declaration of okhttp version from hdfs-client to hadoop-project POM
Date Fri, 17 Mar 2017 01:20:42 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Arpit Agarwal updated HDFS-10394:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-alpha3
           Status: Resolved  (was: Patch Available)

I've committed this. Thanks for the contribution [~xiaobingo].

> move declaration of okhttp version from hdfs-client to hadoop-project POM
> -------------------------------------------------------------------------
>                 Key: HDFS-10394
>                 URL: https://issues.apache.org/jira/browse/HDFS-10394
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Xiaobing Zhou
>            Priority: Minor
>             Fix For: 2.9.0, 3.0.0-alpha3
>         Attachments: HDFS-10394.000.patch, HDFS-10394.001.patch, HDFS-10394.002.patch
> The POM dependency on okhttp in hadoop-hdfs-client declares its version in that POM instead.
> the root declaration, including version, must go into the hadoop-project/pom.xml so that
its easy to track use and have only one place if this version were ever to be incremented.
As it stands, if any other module picked up the library, they could adopt a different version.

This message was sent by Atlassian JIRA

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

View raw message