You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Liptak (JIRA)" <ji...@apache.org> on 2015/07/01 03:40:04 UTC

[jira] [Updated] (HADOOP-12048) many undeclared used dependencies (and declared unused dependencies)

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

Gabor Liptak updated HADOOP-12048:
----------------------------------
    Status: Open  (was: Patch Available)

I would like to work this in phases. I submitted HADOOP-12168 as the first set.

> many undeclared used dependencies (and declared unused dependencies)
> --------------------------------------------------------------------
>
>                 Key: HADOOP-12048
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12048
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.0.0
>            Reporter: Sangjin Lee
>            Assignee: Gabor Liptak
>         Attachments: HADOOP-12048.1.patch, HADOOP-12048.2.patch, HADOOP-12048.3.patch, dependency-analysis.txt, hadoop-unused.txt
>
>
> Currently there are numerous undeclared used dependencies and declared unused dependencies in the hadoop projects.
> Undeclared used dependencies are easier errors to correct, and correcting them will lead to a better management of dependencies (enabling stricter dependency frameworks down the road).
> Declared unused dependencies are harder to resolve, as many may be legitimate runtime dependencies. But fixing them would lead to smaller profiles for hadoop projects.
> We can do a one-time scan of dependency issues and fix them. However, in the long run, it would be nice to be able to enforce those rules via maven plug-in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)