Skip to content
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

Merged
merged 7 commits into from
Nov 28, 2022

Conversation

JCash
Copy link
Contributor

@JCash JCash commented Nov 28, 2022

No description provided.

Comment on lines +186 to +190
String java_home = System.getenv("JAVA_HOME");
if (java_home != null)
{
processExecutor.putEnv("JAVA_HOME", java_home);
}
Copy link
Contributor Author

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"]

Comment on lines +136 to +139
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
throw new ExtenderException(sw.toString());
Copy link
Contributor Author

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?

@JCash JCash changed the base branch from dev to beta November 28, 2022 13:34
@JCash JCash merged commit 13c6bfc into beta Nov 28, 2022
@JCash JCash deleted the java-home-null-fix branch November 28, 2022 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants