hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4497) commons-daemon 1.0.3 dependency has bad group id causing build issues
Date Thu, 14 Feb 2013 20:07:12 GMT

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

Chris Nauroth commented on HDFS-4497:

A side note: commons-daemon stopped distributing pre-compiled packages for the native code
for all platforms except Windows after version 1.0.5.  This includes Linux.

On branch-1, the build.xml contains code to bundle the Linux native package, so we wouldn't
be able to backport this change to branch-1, at least not in a backwards-compatible way. 
We'd have to advise users to build the native code themselves.

I couldn't find equivalent build code on trunk for bundling the Linux native bits, so maybe
this is not a concern for trunk.



> 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
> 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

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

View raw message