Return-Path: 
 <hdfs-issues-return-48355-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 66EF9D58C
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed,  5 Sep 2012 14:02:51 +0000 (UTC)
Received: (qmail 61600 invoked by uid 500); 5 Sep 2012 14:02:51 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 61568 invoked by uid 500); 5 Sep 2012 14:02:51 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 61559 invoked by uid 99); 5 Sep 2012 14:02:51 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 14:02:51 +0000
Date: Thu, 6 Sep 2012 01:02:51 +1100 (NCT)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <409690183.38974.1346853771173.JavaMail.jiratomcat@arcas>
In-Reply-To: <1259325530.13770.1346273948264.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HDFS-3866) HttpFS POM should have property
 where to download tomcat from
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hudson commented on HDFS-3866:
------------------------------

Integrated in Hadoop-Mapreduce-trunk #1187 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1187/])
    HDFS-3866. HttpFS POM should have property where to download tomcat from (zero45 via tucu) (Revision 1380927)

     Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1380927
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/pom.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

                
> HttpFS POM should have property where to download tomcat from
> -------------------------------------------------------------
>
>                 Key: HDFS-3866
>                 URL: https://issues.apache.org/jira/browse/HDFS-3866
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.0.0-alpha
>         Environment: CDH4 build on CentOS 6.2
>            Reporter: Ryan Hennig
>            Assignee: Plamen Jeliazkov
>            Priority: Minor
>             Fix For: 2.2.0-alpha
>
>         Attachments: HDFS-3866.patch
>
>
> When trying to enable a build of CDH4 in Jenkins, I got a build error due to an attempt to download Tomcat from the internet directly instead of via Maven and thus our internal Maven repository.
> The problem is due to this line in src/hadoop-hdfs-project/hadoop-hdfs-httpfs/target/antrun/build-main.xml:
>   <get dest="downloads/tomcat.tar.gz" skipexisting="true" verbose="true" src="http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.32/bin/apache-tomcat-6.0.32.tar.gz"/>
> This build.xml is generated from src/hadoop-hdfs-project/hadoop-hdfs-httpfs/pom.xml:
> <get src="http://archive.apache.org/dist/tomcat/tomcat-6/v${tomcat.version}/bin/apache-tomcat-${tomcat.version}.tar.gz"  dest="downloads/tomcat.tar.gz" verbose="true" skipexisting="true"/>
> Instead of directly downloading from a hardcoded location, the Tomcat dependency should be managed by Maven.  This would enable the use of a local repository for build machines without internet access.

--
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