[jbosstools-issues] [JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure

[Vineet Reynolds (JIRA)]

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

Vineet Reynolds updated JBIDE-16659:
------------------------------------

    Description: 
Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.

When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.

We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents.

  was:
Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.

When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.

We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova prepare android}} or {{cordova prepare ios}} commands.


    
> Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-16659
>                 URL: https://issues.jboss.org/browse/JBIDE-16659
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: aerogear-hybrid
>    Affects Versions: 4.1.1.Final
>            Reporter: Vineet Reynolds
>
> Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories.
> When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode.
> We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira