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] [Commented] (HDFS-10394) move declaration of okhttp version from hdfs-client to hadoop-project POM
Date Thu, 16 Mar 2017 20:35:41 GMT

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

Arpit Agarwal commented on HDFS-10394:

You don't need to declare the okhttp version in hadoop-hdfs-project/hadoop-hdfs-client/pom.xml
(just leave out the version field). Also since okhttp.version is used in just one place you
can eliminate the variable and use the version string directly in the hadoop-project/pom.xml
dependency section.

> 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
>         Attachments: HDFS-10394.000.patch, HDFS-10394.001.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