cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-8153) Cordova Browserify based prepare should still create a plugin metadata file.
Date Mon, 15 Dec 2014 15:42:13 GMT

    [ https://issues.apache.org/jira/browse/CB-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246748#comment-14246748
] 

Andrew Grieve commented on CB-8153:
-----------------------------------

It's still the case that config.xml doesn't actually list plugins. It just lists exec() bridge
metadata, which *most* plugins have. Keeping the cordova_plugins.js module seems like the
best option to me.

> 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: Improvement
>          Components: CordovaLib
>            Reporter: Michal Mocny
>            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


Mime
View raw message