[TIMOB-13581] CLI: adding latest version of module with tiapp previously set to latest does not result in rebuild
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Duplicate |
|---|
| Resolution Date | 2013-04-18T20:37:17.000+0000 |
|---|
| Affected Version/s | Release 3.1.0 |
|---|
| Fix Version/s | Release 3.2.0 |
|---|
| Components | CLI |
|---|
| Labels | qe-3.1.0 |
|---|
| Reporter | Dustin Hyde |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2013-04-15T23:39:23.000+0000 |
|---|
| Updated | 2013-12-03T20:53:19.000+0000 |
|---|
Description
CLI: adding latest version of module with tiapp previously set to latest does not result in rebuild.
Test Steps (known case):
1. Open Titanium Studio.
2. Create Titanium Project.
3. Create Android Module Project.
4. Copy module example code to titanium project.
5. Package android module to titanium project.
6. Set TiApp Editor module version to "*" (latest).
7. Run project on Android Device.
8. Edit module version in module project manifest to "2.0".
9. Edit module project "hello world" string in source code to "hello world 2.0".
10. Re-package android module to titanium project.
11. Run project on Android Device.
Actual Result:
The project is not re-built, the old module is used.
Cleaning the project or editing tiapp.xml will result in a re-build.
Attachments
It's worth noting that this is Android-only. iOS does detect module changes.
Dupe of TIMOB-5837.
Closed.