[
https://issues.apache.org/jira/browse/HADOOP-9407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603347#comment-13603347
]
Hudson commented on HADOOP-9407:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1345 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1345/])
HADOOP-9407. commons-daemon 1.0.3 dependency has bad group id causing build
issues. Contributed by Sangjin Lee. (Revision 1456704)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1456704
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-project/pom.xml
> 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
> 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
