Verify JAVA_HOME is set correctly #1587
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our system requirements point that JAVA_HOME must be set, but
tns doctoris not strict about this.With version 1.7.0 of the runtime,
jarsignerfrom $JAVA_HOME/bin/jarsigner will be called explicitly, so we must be sure JAVA_HOME is correct.jarsignerdoes not exist in JRE, so add logic to call it in order to verify that the currently set JAVA_HOME is correct.Validate the information in the following order:
tns build androidwill fail before starting).tns doctorwill print warning in case any of the above check fails.tns build androidand any other Android related build operations will fail.