[ALOY-1063] CLI: `ti clean` should remove/empty `Resources` for Alloy projects
| GitHub Issue | n/a |
|---|
| Type | Improvement |
|---|
| Priority | Medium |
|---|
| Status | Resolved |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2014-12-11T02:04:28.000+0000 |
|---|
| Affected Version/s | n/a |
|---|
| Fix Version/s | Alloy 1.7.0 |
|---|
| Components | Tooling |
|---|
| Labels | alloy, clean, cli |
|---|
| Reporter | Fokke Zandbergen |
|---|
| Assignee | Tim Poulsen |
|---|
| Created | 2014-04-09T09:03:32.000+0000 |
|---|
| Updated | 2014-12-11T02:04:28.000+0000 |
|---|
Description
Problem Description
With the Alloy compiler trying to become smarter in compiling only those files that are changed, it happens more often that for different reasons the Resources directory is not up-to-date anymore. For this reason I'd like to see the Resources folder emptied or removed with ti clean and the Studio options using this CLI command. This way I can instruct people to do a clean as a first attempt to resolve compile/build problems.
Comments
JSON Source
Thanks for your report. The Platform team will set the priority on this.
This is not a TIMOB issue. This is an Alloy issue. Alloy SHOULD NOT be a standalone command line tool. It SHOULD be a Titanium CLI plugin that includes includes a hook into the "clean" command. It should also tie into the "create" command "config" hook to add a --alloy flag, and tie into the "pre-build" hook to compile the app dir into the Resource dir. If the "project" command was finished, we should have a hook in there that allows you to change a Titanium classic app into an Alloy app. In the meantime, we could have an "alloy" command with a "new" subcommand (i.e. ti alloy new).
Sounds like a plan.
PR https://github.com/appcelerator/alloy/pull/630 Adds a CLI hook to empty the resources directory for an Alloy project Functional review: 1. Create a new Alloy project, or in an existing Alloy project, enter
alloy install plugin .to install the new hook 2. Build the project and confirm you have contents in the Resources directory 3. Doti cleanand confirm that Resources is empty (but the dir still exists) 4. Build again 5. Doti clean --shallowand confirm that build was emptied but Resources was notPR merged.