You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/02/15 08:58:00 UTC
[jira] [Created] (HDDS-1113) Remove default dependencies from
hadoop-ozone project
Elek, Marton created HDDS-1113:
----------------------------------
Summary: Remove default dependencies from hadoop-ozone project
Key: HDDS-1113
URL: https://issues.apache.org/jira/browse/HDDS-1113
Project: Hadoop Distributed Data Store
Issue Type: Improvement
Components: build
Reporter: Elek, Marton
Assignee: Elek, Marton
There are two ways to define common dependencies with maven:
1.) put all the dependencies to the parent project and inherit them
2.) get all the dependencies via transitive dependencies
TLDR; I would like to switch from 1 to 2 in hadoop-ozone
My main problem with the first approach that all the child project get a lot of dependencies independent if they need them or not. Let's imagine that I would like to create a new project (for example a java csi implementation) It doesn't need ozone-client, ozone-common etc, in fact it conflicts with ozone-client. But these jars are always added as of now.
Using transitive dependencies is more safe: we can add the dependencies where we need them and all of the other dependent projects will use them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org