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 Fri, 15 Feb 2013 17:17:13 GMT

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

Chris Nauroth commented on HDFS-4497:
-------------------------------------

I just found some more historical background on this.  In HDFS-2303, the community made a
specific choice to stop bundling jsvc on branch-2 and later.  branch-1 continues to bundle
it though.  Considering that, I don't think we necessarily have a requirement to keep the
commons-daemon version in sync between trunk and branch-1.  Therefore, I think it's OK to
upgrade commons-daemon to latest (1.0.13) on trunk as long as we're confident about testing
and compatibility.

                
> 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