hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-222) Remove hdfs command line from ozone distrubution.
Date Wed, 22 Aug 2018 07:52:00 GMT

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

Elek, Marton commented on HDDS-222:

I prefer to change all the dependencies to compile level unless we have a strong reason to
keep it on provided. According to the maven nomenclature they should be compile scope anyway.
Provided was used just as a workaround (IMHO).

According to this page: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

{quote}provided:  This is much like compile, but indicates you expect the JDK or a container
to provide the dependency at runtime. For example, when building a web application for the
Java Enterprise Edition, you would set the dependency on the Servlet API and related Java
EE APIs to scope provided because the web container provides those classes{quote}

I think it's not our use case. We need the dependencies and the jars should be there.

Compile time dependency also helps a lot to start the service components from IDE.

> Remove hdfs command line from ozone distrubution.
> -------------------------------------------------
>                 Key: HDDS-222
>                 URL: https://issues.apache.org/jira/browse/HDDS-222
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: newbie
>             Fix For: 0.2.1
>         Attachments: HDDS-222.001.patch, HDDS-222.002.patch
> As the ozone release artifact doesn't contain a stable namenode/datanode code the hdfs
command should be removed from the ozone artifact.
> ozone-dist-layout-stitching also could be simplified to copy only the required jar files
(we don't need to copy the namenode/datanode server side jars, just the common artifacts

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