You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2011/07/30 01:34:10 UTC
[jira] [Commented] (MAPREDUCE-2753) Generated POMs hardcode
dependency on hadoop-common version 0.22.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/MAPREDUCE-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073072#comment-13073072 ]
Joep Rottinghuis commented on MAPREDUCE-2753:
---------------------------------------------
Uploaded new patch MAPREDUCE-2753-1.patch
> Generated POMs hardcode dependency on hadoop-common version 0.22.0-SNAPSHOT
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-2753
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2753
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build
> Affects Versions: 0.22.0
> Environment: RHEL 6.1 & Ubuntu 11.04; Sun JDK 1.6_016 & Sun JDK 1.6.0_26; Ant 1.8.2
> Reporter: Joep Rottinghuis
> Attachments: MAPREDUCE-2753-1.patch, MAPREDUCE-2753.patch
>
>
> The generated poms inject the version of mapred itself, but hardcode the version of hadoop-common they depend on.
> When trying to build downstream projects (HBase), then they will require hadoop-common-0.22.0-SNAPSHOT.jar instead of the version they compiled against.
> When trying to do an offline build this will fail to resolve as another hadoop-common has been installed in the local maven repo.
> Even during online build, it should compile against the hadoop-common that hdfs compiled against.
> When versions mismatch one cannot do a coherent build. That is particularly problematic when making simultaneous change in hadoop-common and hadoop-mapreduce and you want to try this locally before committing each.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira