You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Steve Gill (JIRA)" <ji...@apache.org> on 2015/04/06 20:32:13 UTC
[jira] [Updated] (CB-8153) Cordova Browserify based prepare should
still create a plugin metadata file.
[ https://issues.apache.org/jira/browse/CB-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gill updated CB-8153:
---------------------------
Issue Type: Sub-task (was: Improvement)
Parent: CB-8801
> Cordova Browserify based prepare should still create a plugin metadata file.
> ----------------------------------------------------------------------------
>
> Key: CB-8153
> URL: https://issues.apache.org/jira/browse/CB-8153
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: CordovaLib
> Reporter: Michal Mocny
> Assignee: Steve Gill
> Priority: Minor
>
> If we move away from cordova_plugins.js and onto browserify concat for plugin js modules, it would still be useful to retain some plugin metadata file.
> Hopefully it can be as simple as a json file with { pluginId: pluginVersion } or something like that.
> Being able to quickly figure out which plugins a given app was built with has come up as useful in the past, even if only for informational purposes!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org