Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 28 Jul 2011 23:02:09 +0000 (UTC)
From: "Joep Rottinghuis (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <1051555308.16988.1311894129913.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-2214) Generated POMs hardcode dependency on
 hadoop-common version 0.22.0-SNAPSHOT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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