[TIMOB-3605] Android: Build Fastdev projects with all modules initially
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-05-12T23:53:15.000+0000 |
| Affected Version/s | Release 1.7.0 |
| Fix Version/s | Release 1.7.0, Sprint 2011-18 |
| Components | Android |
| Labels | android, fastdev, feature |
| Reporter | Marshall Culpepper |
| Assignee | Bill Dawson |
| Created | 2011-04-18T09:06:37.000+0000 |
| Updated | 2012-05-14T14:35:38.000+0000 |
Description
In FastDev mode, we don't recompile the project to detect which modules are (or aren't) used. The initial build of a Fastdev app should enable all modules, so there aren't any weird consequences of using undetected modules in fast turnaround.
I have added sub-types of Release type in Task Type field. Can you pick specific sub-type to unbind 'Release' type, please ?.
Re-opening to look more closely at problem when building first on emulator then immediately releasing to device.
Test my changes merged with Marshall's recent big fastdev-related changes. tested several scenarios and realized part of my code from previous commit wasn't necessary. Ripped it out and retested several scenarios.
verified on emulator 2.2