[
https://issues.apache.org/jira/browse/CB-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244918#comment-14244918
]
Steve Gill commented on CB-8153:
--------------------------------
I see some value in keeping this available in the project (instead of relying
only on cordova plugin ls which works great). I think the usecase of unpacking
apk is a little weak since it is something we never promote and probably don't
want to encourage.
Why don't we add the version of the plugin to config.xml. It already lists the
plugins in there.
Or alternatively, if we do want to stick with json, lets create a package.json
and start adding that to every cordova project by default. We can slowly start
moving stuff out of config.xml into package.json and have our tools look at
both files. Work towards the whole a cordova project is a node project thing.
That way we can use node modules + browserify in developing cordova apps ;) One
can dream right :)
> 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-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
