Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E6D75200CF0 for ; Thu, 7 Sep 2017 23:36:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E56241609D9; Thu, 7 Sep 2017 21:36:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 372D616098B for ; Thu, 7 Sep 2017 23:36:11 +0200 (CEST) Received: (qmail 75745 invoked by uid 500); 7 Sep 2017 21:36:09 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 75734 invoked by uid 99); 7 Sep 2017 21:36:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Sep 2017 21:36:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 49382CE0A4 for ; Thu, 7 Sep 2017 21:36:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id kaMhhQDg9w0e for ; Thu, 7 Sep 2017 21:36:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id ABA7F6104F for ; Thu, 7 Sep 2017 21:36:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 85B73E0F01 for ; Thu, 7 Sep 2017 21:36:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A57AD2416F for ; Thu, 7 Sep 2017 21:36:00 +0000 (UTC) Date: Thu, 7 Sep 2017 21:36:00 +0000 (UTC) From: "Junping Du (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14842) Hadoop 2.8.2 release build process get stuck due to java issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 07 Sep 2017 21:36:12 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157711#comment-16157711 ] Junping Du commented on HADOOP-14842: ------------------------------------- I tried to apply HADOOP-14816 but hitting with many conflicts -almost all for Dockerfile. Sounds like we are missing many patches in branch-2 and 2.8. Do we need to backport all/most of them back to branch-2/2.8? I saw we were upgrading cmake, maven, etc. Some patch like remove JDK 7 should definitely be ignored. Will backport rest of them can cause incompatible issues? If backport is a risky option, It would be nice if we can have a fix for branch-2/branch-2.8 only. > Hadoop 2.8.2 release build process get stuck due to java issue > -------------------------------------------------------------- > > Key: HADOOP-14842 > URL: https://issues.apache.org/jira/browse/HADOOP-14842 > Project: Hadoop Common > Issue Type: Bug > Components: build > Reporter: Junping Du > Priority: Blocker > > In my latest 2.8.2 release build (via docker) get failed, and following errors received: > > {noformat} > "/usr/bin/mvn -Dmaven.repo.local=/maven -pl hadoop-maven-plugins -am clean install > Error: JAVA_HOME is not defined correctly. We cannot execute /usr/lib/jvm/java-7-oracle/bin/java" > {noformat} > This looks like related to HADOOP-14474. However, reverting that patch doesn't work here because build progress will get failed earlier in java download/installation - may be as mentioned in HADOOP-14474, some java 7 download address get changed by Oracle. > Hard coding my local JAVA_HOME to create-release or Dockerfile doesn't work here although it show correct java home. My suspect so far is we still need to download java 7 from somewhere to make build progress continue in docker building process, but haven't got clue to go through this. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org