You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2011/08/22 20:35:29 UTC
[jira] [Assigned] (HDFS-2214) Generated POMs hardcode dependency on
hadoop-common version 0.22.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/HDFS-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joep Rottinghuis reassigned HDFS-2214:
--------------------------------------
Assignee: Joep Rottinghuis
> Generated POMs hardcode dependency on hadoop-common version 0.22.0-SNAPSHOT
> ---------------------------------------------------------------------------
>
> Key: HDFS-2214
> URL: https://issues.apache.org/jira/browse/HDFS-2214
> Project: Hadoop HDFS
> 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
> Assignee: Joep Rottinghuis
> Fix For: 0.22.0
>
> Attachments: HDFS-2214-follow-up.patch, HDFS-2214.patch, HDFS-2214.patch, HDFS-2214.patch, HDFS-2214.patch
>
>
> The generated poms inject the version of hdfs itsel, but hardcode the version of hadoop-common they depend on.
> When trying to build downstream projects for example mapreduce, then they will require hadoop-common-0.22.0-SNAPSHOT.jar.
> 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-hdfs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira