[TIMOB-11641] Have the Android Module build.xml accept and use a Java-Home argument
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2016-08-25T00:04:40.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | n/a |
| Reporter | Shalom Gibly |
| Assignee | Eric Merriman |
| Created | 2012-11-02T00:27:26.000+0000 |
| Updated | 2017-03-17T18:13:34.000+0000 |
Description
This one was created after investigating a Studio ticket - TISTUD-1984
As it looks like, a user has to set a JAVA_HOME environment variable in the system. Failing to do so triggers an error from the build.xml for Android module packaging.
Since the Studio does not use an external process to initiate Ant, we need an additional variable support in the 'build.xml' to accept and use a specified java-home.
The studio detects a valid Java Home (one that contains bin/javac), even when it's not specified in the environment. The detected location can then be passed into the 'build.xml' as an argument. Something like "java_home".
The Android module build no longer uses Ant or the
build.xmlfile. Furthermore, the Android module build uses node-appc's JDK detection library which finds the JDK based on theJAVA_HOMEenvironment variable and via the Titanium CLI configjava.homeoverride.Closing ticket as invalid.