[ 
https://issues.apache.org/jira/browse/HADOOP-14842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated HADOOP-14842:
--------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.2
                   2.9.0
           Status: Resolved  (was: Patch Available)

Thanks [~xgong] for quick review. Commit it to branch-2, branch-2.8 and 
branch-2.8.2.

> 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
>            Assignee: Junping Du
>            Priority: Blocker
>             Fix For: 2.9.0, 2.8.2
>
>         Attachments: HADOOP-14842-branch-2.8-2.002.patch, 
> HADOOP-14842.branch-2.8-2.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to