[TIMOB-18534] Tooling: CLI Scans Module folders for platforms that are not targeted.

GitHub Issue	n/a
Type	Improvement
Priority	Medium
Status	Closed
Resolution	Invalid
Resolution Date	2020-01-30T10:20:43.000+0000
Affected Version/s	n/a
Fix Version/s	n/a
Components	CLI
Labels	n/a
Reporter	Stephen Feather
Assignee	Chris Barber
Created	2015-02-06T21:59:04.000+0000
Updated	2020-01-31T11:20:28.000+0000

Description

Whats Expected

That tooling only concern itself with modules related to the targeted build platform

What Happens

When building with iOS as the target platform, the tooling scans the default module location in which android modules are stored:

[DEBUG] Detected android module: com.appcelerator.apm 1.1.1 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/com.appcelerator.apm/1.1.1
[DEBUG] Detected android module: facebook 3.0.2 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/facebook/3.0.2
[DEBUG] Detected android module: facebook 3.0.3 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/facebook/3.0.3
[DEBUG] Detected android module: ti.cloudpush 3.3.7 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/ti.cloudpush/3.3.7
[DEBUG] Detected android module: ti.map 2.2.3 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/ti.map/2.2.3
[DEBUG] Detected android module: ti.paypal 2.2.2 @ /Users/stephenfeather/Library/Application Support/Titanium/modules/android/ti.paypal/2.2.2

Comments

Chris Barber 2020-01-30

This is by design. It's simply detecting what modules are installed. This detection code is run independent of which platform you're building for.
Sohail Saddique 2020-01-31

Ticket closed.

JSON Source