You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by lb...@apache.org on 2019/01/21 11:18:55 UTC

[camel-k] branch master updated: chore(contributing.adoc): Add explanation to add KOTLIN_JDK_HOME for building on MacOs

This is an automated email from the ASF dual-hosted git repository.

lburgazzoli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/master by this push:
     new 3a3a086  chore(contributing.adoc): Add explanation to add KOTLIN_JDK_HOME for building on MacOs
3a3a086 is described below

commit 3a3a0863f28e92d64ce607eb388f0addb44b68bc
Author: Roland Huß <ro...@ro14nd.de>
AuthorDate: Mon Jan 21 08:47:09 2019 +0100

    chore(contributing.adoc): Add explanation to add KOTLIN_JDK_HOME for building on MacOs
    
    As this seems to be a temporary workaround, just let document it.
    Otherwise it would have made sense to adapt the Makefile to set it
    automatically.
    
    Fixes #297.
---
 contributing.adoc | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/contributing.adoc b/contributing.adoc
index d91cb58..d8c1904 100644
--- a/contributing.adoc
+++ b/contributing.adoc
@@ -72,6 +72,16 @@ make dep
 
 The `make dep` command runs `dep ensure -v` under the hood, so make sure that `dep` is properly installed.
 
+For now, you have to set environment variable `KOTLIN_JDK_HOME` pointing to your JDK (not JRE) home directory.
+Also ensure, that you are using a Java version 8.
+
+For Mac you can just do a
+
+[source, bash]
+----
+export KOTLIN_JDK_HOME=$(/usr/libexec/java_home -v 1.8)
+----
+
 To build the whole project you now need to run:
 
 ```
@@ -182,4 +192,4 @@ After you setup the IDE task, you can run and debug the operator process.
 
 NOTE: The operator can be fully debugged in Minishift, because it uses OpenShift S2I binary builds under the hood.
 The build phase cannot be (currently) debugged in Minikube because the Kaniko builder requires that the operator and the publisher pod
-share a common persistent volume.
\ No newline at end of file
+share a common persistent volume.