-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't add environment variables that are null to the ProcessExecutor #251
Conversation
String java_home = System.getenv("JAVA_HOME"); | ||
if (java_home != null) | ||
{ | ||
processExecutor.putEnv("JAVA_HOME", java_home); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently haven't setup the JAVA_HOME on the darwin server.
We'll need it for the Rive extension, since we are building jni stuff, and we need the java sdk (jni.h):
defold-rive/ext.manifest
includes: ["{{env.JAVA_HOME}}/include/linux", "{{env.JAVA_HOME}}/include"]
StringWriter sw = new StringWriter(); | ||
PrintWriter pw = new PrintWriter(sw); | ||
e.printStackTrace(pw); | ||
throw new ExtenderException(sw.toString()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually prints out the full callstack of the error.
I guess the cause, had another cause and we didn't iterate it?
No description provided.