brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ygy <...@git.apache.org>
Subject [GitHub] brooklyn-library pull request: Fix: ElasticSearch used Java versio...
Date Fri, 25 Mar 2016 13:46:53 GMT
GitHub user ygy opened a pull request:

    https://github.com/apache/brooklyn-library/pull/26

    Fix: ElasticSearch used Java version

    Making ElasticSearch to use JavaSoftwareProcessDriver so the correct
    java version is installed. ElasticSearch used to install java via
    BashCommands#installJavaLatestOrWarn(). It prevents setting the
    installed java version as default when:
    - the VM image comes with preinstalled jdk 6 or jdk7
    - CentOS version of JDK8 doesn't update the default automatically

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ygy/brooklyn-library fix/es-used-java

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-library/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #26
    
----
commit c8a450c039911f14dbf196aabdf0927ce543503e
Author: Yavor Yanchev <yavor@yanchev.com>
Date:   2016-03-25T13:44:27Z

    Fix: ElasticSearch used Java version
    
    Making ElasticSearch to use JavaSoftwareProcessDriver so the correct
    java version is installed. ElasticSearch used to install java via
    BashCommands#installJavaLatestOrWarn(). It prevents setting the
    installed java version as default when:
    - the VM image comes with preinstalled jdk 6 or jdk7
    - CentOS version of JDK8 doesn't update the default automatically

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message