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 "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2013/04/17 22:45:18 UTC

[jira] [Updated] (HADOOP-9407) commons-daemon 1.0.3 dependency has bad group id causing build issues

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

Konstantin Boudnik updated HADOOP-9407:
---------------------------------------

    Affects Version/s: 2.0.4-alpha
    
> commons-daemon 1.0.3 dependency has bad group id causing build issues
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-9407
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9407
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.0.3-alpha, 2.0.4-alpha
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>             Fix For: 2.0.5-beta
>
>         Attachments: HDFS-4497.patch
>
>
> The commons-daemon dependency of the hadoop-hdfs module has been at version 1.0.3 for a while. However, 1.0.3 has a pretty well-known groupId error in its pom ("org.apache.commons" as opposed to "commons-daemon"). This problem has since been corrected on commons-daemon starting 1.0.4.
> This causes build problems for many who depend on hadoop-hdfs directly and indirectly, however. Maven can skip over this metadata inconsistency. But other less forgiving build systems such as ivy and gradle have much harder time working around this problem. For example, in gradle, pretty much the only obvious way to work around this is to override this dependency version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira