[TIMOB-12367] CLI: More elegant solution for users that delete or have not selected SDK
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-08-02T23:19:01.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | 2013 Sprint 16, 2013 Sprint 16 Core, Release 3.2.0 |
| Components | CLI |
| Labels | n/a |
| Reporter | Eric Merriman |
| Assignee | Chris Barber |
| Created | 2013-01-22T02:20:49.000+0000 |
| Updated | 2013-11-18T17:57:49.000+0000 |
Description
While creating additional test cases for the CLI, it became evident that users that either delete the currently active SDK or in some cases have never selected one will encounter strange issues that are not evident how to fix.
The workaround is to use ti sdk select to choose an active build
Steps to reproduce:
1) Use ti sdk to list your sdks
2) Delete the active sdk from your system using the finder (using ti sdk uninstall will set another sdk as active)
3) perform a ti build -h
Result:
[ERROR] "build" is an unrecognized command.
https://github.com/appcelerator/titanium/pull/50 https://github.com/appcelerator/node-appc/pull/50
To test: 1. Rename the "mobilesdk" folder to "mobilesdk2" where your Titanium SDKs are installed 2. Run "ti sdk" to verify there are no SDKs installed 3. Run "ti" and notice there are no SDK level commands (build, clean, create, project) 4. Run "ti build" and instead of showing an unknown command, it will say you need to install a Titanium SDK To restore your system, rename your "mobilesdk2" folder back to "mobilesdk".
Verified fixed on: Mac OSX 10.9 Mavericks Titanium Studio, build: 3.2.0.201311160316 Titanium SDK, build: 3.2.0.v20131117001643 CLI: 3.2.0-alpha Alloy: 1.3.0 CLI provides message telling user to install a Titanium SDK, rather than just displaying an error message about unknown commands. Closing.