[jbosstools-issues] [JBoss JIRA] (JBIDE-17203) Cordova project requires user to recreate run configuration when iOS target sdk is changed

[Gorkem Ercan (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gorkem Ercan resolved JBIDE-17203.
----------------------------------
    Resolution: Won't Fix


We have a new implementation, for "Run on iOS Simulator". With the new changes iOS builder detects the SDK that the selected Device uses and compiles with that SDK. I think switching the device from launch configuration dialog will be sufficient in this case. 
I guess an SDK requirement change would happen with changes to either used engine or introduction/update of a plugin but in both cases we do not have an easy way to detect such a change.

I think regenerating the launch configuration does not help in this case because we do not know what SDK to target.  We can always target the latest installed SDK but that may not necessarily be the required SDK.  With the new launch configuration it is less useful because SDK is part of the Device definition managed on the iOS simulator manager.

> Cordova project requires user to recreate run configuration when iOS target sdk is changed
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-17203
>                 URL: https://issues.jboss.org/browse/JBIDE-17203
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: aerogear-hybrid
>            Reporter: Tadeas Kriz
>            Assignee: Gorkem Ercan
>             Fix For: 4.3.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> When cordova application is changed that way that it requires newer iOS target SDK (for example switching from iOS 6 to iOS 7) it will no longer compile unless the user deletes and then makes a new run configuration. It would be good if the user might select which target sdk will be used, this will probably mitigate this issue.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)