cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Mocny (JIRA)" <>
Subject [jira] [Commented] (CB-4358) Trim amount of frameworks (18) in default template to minimum needed (4)
Date Tue, 23 Jul 2013 14:50:49 GMT


Michal Mocny commented on CB-4358:

The problem of handling plugin/platform removal comes up a lot for various reasons like this.
 Its hard to know what to clean up, especially in the face of overlap with other plugins.
 What if we just clear everything and re-build that project artifacts from scratch, i.e. re-install
all remaining plugins?  As-is, this would mean trouncing on any user-changes inside platforms,
but we already signal that those files are not the be modified don't we?  We should support
long-lived places for those types of user changes, such as the app manifest.

Is that feasible?  I think Joe often points out that external devs do make changes to platforms
even against suggestion.
> Trim amount of frameworks (18) in default template  to minimum needed (4)
> -------------------------------------------------------------------------
>                 Key: CB-4358
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 3.0.0
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>             Fix For: 3.1.0
> These are the only 4 frameworks needed for 3.0.0 with just CordovaLib:
> - MobileCoreServices.framework
> - CoreGraphics.framework
> - CoreLocation.framework
> - AssetsLibrary.framework
> Ensure the default template only ships with these, right now it ships with 18 frameworks
> NOTE: After doing this, re-test all core plugins, I'm sure some of them will fail since
they probably depend on the frameworks already existing in the default template. The frameworks
they need will have to be specified in their plugin.xml (file separate bugs for each plugin)

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:

View raw message