hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (HDDS-1597) Remove hdds-server-scm dependency from ozone-common
Date Mon, 03 Jun 2019 06:37:00 GMT

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

Elek, Marton reopened HDDS-1597:

> Remove hdds-server-scm dependency from ozone-common
> ---------------------------------------------------
>                 Key: HDDS-1597
>                 URL: https://issues.apache.org/jira/browse/HDDS-1597
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.4.1
>         Attachments: ozone-dependency.png
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
> I noticed that the hadoop-ozone/common project depends on hadoop-hdds-server-scm project.
> The common projects are designed to be a shared artifacts between client and server side.
Adding additional dependency to the common pom means that the dependency will be available
for all the clients as well.
> (See the attached artifact about the current, desired structure).
> We definitely don't need scm server dependency on the client side.
> The code dependency is just one class (ScmUtils) and the shared code can be easily moved
to the common.

This message was sent by Atlassian JIRA

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

View raw message