[jbosstools-issues] [JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

[Gorkem Ercan (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055794#comment-13055794 ] 

Gorkem Ercan commented on JBDS-3394:
------------------------------------


a) I do not know about examples (not even sure what examples we are referring to ) but we are not dropping the support for building/running engines older than 3.5.0. We are basically synching the list of downloadable engines with Cordova CLI. Also Cordova CLI did not have engine pinning supported until a month ago and we handle our own pinning (see b for details) so I am not sure what would be updated.

b) If the project is referring to an earlier than 3.5.0 engine and you have the engine available locally nothing will happen. We support running those engines. If the engine is not present locally, we will prompt that the selected engine is not present and ask users to select one. In this case user either needs to download manually and install or select a 3.5.0 or later platform.

> Use cordova platform downloads from npm
> ---------------------------------------
>
>                 Key: JBDS-3394
>                 URL: https://issues.jboss.org/browse/JBDS-3394
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: aerogear-hybrid
>            Reporter: Gorkem Ercan
>            Assignee: Gorkem Ercan
>             Fix For: 9.0.0.Alpha2
>
>
> Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. 
> Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm.
> cordova-ios 
>  ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ]
> cordova-android
> [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ]
> cordova-wp8
> [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ]



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)