[TIMOB-14026] CLI: Make sure sdk folder is writable when installing an sdk
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-08-02T23:18:49.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 16, 2013 Sprint 16 Core, Release 3.2.0 |
| Components | CLI |
| Labels | n/a |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2013-05-30T16:14:03.000+0000 |
| Updated | 2013-11-18T18:34:30.000+0000 |
Description
If the mobile sdk folder is not writable, the sdk install command errors. Try to detect and gracefully fail.
https://github.com/appcelerator/titanium/pull/50 https://github.com/appcelerator/node-appc/pull/50
To test, run the "ti sdk" command to determine the default Titanium SDK install location. For Mac OS X, the default install location is "~/Library/Application Support/Titanium". Next, run:
Then run "titanium sdk install --branch master" to try to download the latest SDK. The install will fail and the SDK is not downloaded. To restore your folder permissions, run: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 Verified using test case provided in comments and SDK successfully installed to writable folder and an error message is displayed for folders that have no write access. Closing.