[TIMOB-16085] CLI: JDK detect does not support JAVA_HOME that begins with ~
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-01-18T00:23:13.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2014 Sprint 01, 2014 Sprint 01 Core, Release 3.2.3, Release 3.3.0 |
| Components | CLI |
| Labels | qe-closed-3.2.3, qe-testadded |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2013-12-26T19:14:27.000+0000 |
| Updated | 2014-03-26T23:00:10.000+0000 |
Description
If JAVA_HOME is set to "~/some/path/to/jdk", then it will not properly resolve the path and in effect will not be able to find the JDK.
node-appc master pull request: https://github.com/appcelerator/node-appc/pull/80 node-appc 3.2.x pull request: https://github.com/appcelerator/node-appc/pull/81
This will probably need to be tested on Windows. If you set the JAVA_HOME to begin with a tilde, then it will do the right thing and resolve it for you. Windows will not.
Tested on windows8.1 Set JAVA_HOME to begin with tilde, and ran "ti info", as a result - no java was found. Otherwise, "ti info" returns the correct path. Node.JS Version: v0.10.13 NPM Version: 1.3.2 /usr/local/lib ├── acs@1.0.14 ├── alloy@1.3.1 ├── npm@1.3.2 ├── titanium@3.2.3-dev └── titanium-code-processor@1.1.0