[TIMOB-5837] Tooling: Adding a module requires a clean build
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-10-19T01:17:10.000+0000 |
| Affected Version/s | Release 1.7.0 |
| Fix Version/s | 2013 Sprint 21, 2013 Sprint 21 Core, Release 3.2.0 |
| Components | Android, iOS, Tooling |
| Labels | androidbuild, cb-verified, qe-3.1.0 |
| Reporter | Matthew Apperson |
| Assignee | Chris Barber |
| Created | 2011-10-24T06:03:39.000+0000 |
| Updated | 2013-11-06T19:40:16.000+0000 |
Description
Currently when a new 3rd party module is added to the code and TiApp.xml file, the user must also do a clean build rather then Titanium detecting that the newly requested module is available and including it automatically
Bump. Can we get this into 2.2? Note I am resolving a ticket as a duplicate of this issue from Jeff H.
I just added support for this in the new CLI. It's up to Ingo if he wants this backported.
Just an update on this: iOS: The old iphone builder.py script does not check for changes to the tiapp.xml nor the modules themselves. The new CLI's iOS build command DOES check for changes to the tiapp.xml, but not the actual modules. Android: The old android builder.py scripts does not check for changes to the tiapp.xml nor the modules themselves. Since the new CLI's android build command wraps the android python command, the problem remains. Mobile Web: Mobile Web always does a clean rebuild, so it's a non-issue.
The new Android build finally supports this.
PR: https://github.com/appcelerator/titanium_mobile/pull/4781
Verified fixed on: Mac OSX 10.9 Mavericks Titanium Studio, build: 3.2.0.201311060354 Titanium SDK, build: 3.2.0.v20131105162443 CLI: 3.2.0 Alloy: 1.3.0 Project does not require a clean build after adding a new module to the project. Building straight after adding a new module runs successfully. Closing.