hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4497) commons-daemon 1.0.3 dependency has bad group id causing build issues
Date Wed, 13 Feb 2013 23:24:12 GMT

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

Sangjin Lee updated HDFS-4497:
------------------------------

    Status: Open  (was: Patch Available)
    
> commons-daemon 1.0.3 dependency has bad group id causing build issues
> ---------------------------------------------------------------------
>
>                 Key: HDFS-4497
>                 URL: https://issues.apache.org/jira/browse/HDFS-4497
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sangjin Lee
>         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

Mime
View raw message