[jira] [Resolved] (CB-3058) changes should be handled in prepare module

["Filip Maj (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CB-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Maj resolved CB-3058.
---------------------------

    Resolution: Fixed

all done woot
                
> <config-file> changes should be handled in prepare module
> ---------------------------------------------------------
>
>                 Key: CB-3058
>                 URL: https://issues.apache.org/jira/browse/CB-3058
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Plugman
>            Reporter: Filip Maj
>            Assignee: Filip Maj
>              Labels: future
>
> With support multiple plugins and {{<config-file>}} being a shared space in application manifests that plugins can modify, plugman needs to be aware of how to handle changing the configuration files.
> In the case of installing a new plugin, things are added into the appropriate config-file if they do not exist. This is great and works fine.
> In the case of uninstalling a plugin, this is trickier. Consider two plugins, A and B, that share the same requirement for a manifest change (e.g. both require camera permission). When you go to uninstall plugin A, you would still want the camera permission to remain in the native manifest as it is required by plugin B.
> One solution is that uninstalling plugin A causes uninstallation of all plugins, followed by re-installation of all plugins minus plugin A.
> Another solution is to implement a "smart" module in plugman that is aware of the native config files, how many different plugins are installed into an app, and what difference of config file changes between plugins exist so that uninstallation of a single plugin only removes unused bits from the native config manifests.

--
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