mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Klues (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-4184) Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'
Date Wed, 16 Dec 2015 23:28:46 GMT

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

Kevin Klues updated MESOS-4184:
-------------------------------
    Description: 
Jenkins builds are now consistently failing for centos 7, withe the failure:

checking value of Java system property 'java.home'...
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
configure: error: could not guess JAVA_HOME

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as make sure
the proper versions of java are installed during the installation process.

The problem here is that we install maven BEFORE installing java-1.7.0-openjdk-devel, causing
maven to pull in a dependency on java-1.8.0-openjdk. This causes problems with finding the
proper java.home in our mesos/configure script because of the mismatch between the most up
to date jre (1.8.0) and the most up to date development tools (1.7.0).  We can either update
the script to pull in the 1.8 devel tools or move our dependence on maven until AFTER our
installation of java-1.7.0-openjdk-devel.  Unclear what the best solution is.

  was:
Jenkins builds are now consistently failing for centos 7, withe the failure:

checking value of Java system property 'java.home'...
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
configure: error: could not guess JAVA_HOME

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as make sure
the proper versions of java are installed during the installation process.

The problem here is that This is that we install maven
BEFORE installing java-1.7.0-openjdk-devel, causing maven to pull in a dependency on java-1.8.0-openjdk.
This causes problems with finding the proper java.home in our mesos/configure script because
of the mismatch between the most up to date jre (1.8.0) and the most up to date development
tools (1.7.0).  We can either update the script to pull in the 1.8 devel tools or move our
dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel.  Unclear what
the best solution is.


> Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'
> -------------------------------------------------------------------------------------
>
>                 Key: MESOS-4184
>                 URL: https://issues.apache.org/jira/browse/MESOS-4184
>             Project: Mesos
>          Issue Type: Bug
>          Components: jenkins
>         Environment: centos 7
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>
> Jenkins builds are now consistently failing for centos 7, withe the failure:
> checking value of Java system property 'java.home'...
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre
> configure: error: could not guess JAVA_HOME
> They also fail early on during 'bootstrap' with a missing 'which' command.
> The solution is to update support/docker_build.sh to install 'which' as well as make
sure the proper versions of java are installed during the installation process.
> The problem here is that we install maven BEFORE installing java-1.7.0-openjdk-devel,
causing maven to pull in a dependency on java-1.8.0-openjdk. This causes problems with finding
the proper java.home in our mesos/configure script because of the mismatch between the most
up to date jre (1.8.0) and the most up to date development tools (1.7.0).  We can either update
the script to pull in the 1.8 devel tools or move our dependence on maven until AFTER our
installation of java-1.7.0-openjdk-devel.  Unclear what the best solution is.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message