[TIMOB-18535] Tooling: CLI Scans Module folders when no modules are declared in tiapp.xml
| GitHub Issue | n/a |
|---|
| Type | Improvement |
|---|
| Priority | Medium |
|---|
| Status | Closed |
|---|
| Resolution | Invalid |
|---|
| Resolution Date | 2020-01-30T10:22:56.000+0000 |
|---|
| Affected Version/s | n/a |
|---|
| Fix Version/s | n/a |
|---|
| Components | CLI, Tooling |
|---|
| Labels | n/a |
|---|
| Reporter | Stephen Feather |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2015-02-06T22:09:30.000+0000 |
|---|
| Updated | 2020-01-31T11:23:56.000+0000 |
|---|
Description
Expected
That the tooling efficiently builds, skipping over process that are not required
What Happens
Tooling will scan the default module storage location even if no modules are declared in the tiapp.xml
Reproduce
Create an empty project. Build for device. See that the tooling inventories installed modules even though none are in the tiapp.xml
Comments
JSON Source
This is by design. This detection code is run independent of whether or not you have any modules in your tiapp.xml. This will become less of a performance issue in the next major CLI release.
Ticket closed.