[
https://issues.apache.org/jira/browse/CB-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202258#comment-15202258
]
ASF GitHub Bot commented on CB-10679:
-------------------------------------
Github user stevengill commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/559#discussion_r56729389
--- Diff: www/_posts/2016-03-16-new-plugin-fetching.md ---
@@ -0,0 +1,46 @@
+---
+layout: post
+author:
+ name: Richard Knoll
+ url: https://github.com/riknoll
+title: "Upcoming Changes to Plugin Fetching"
+categories: announcements
+tags: news
+---
+
+The Cordova 6.0.0 release introduced the pinning of core plugin
+versions in cordova-lib.
+
+We are happy to announce that one of the new features in the upcoming
+Cordova 6.1.0 release is a general API that allows any plugin to guide
+the CLI in choosing a compatible plugin release to fetch for a given
project.
+This moves the plugin dependency information out of cordova-lib so that it
+can update independently of the Cordova tools and support third-party
plugins
+outside of core. Our hope is that this feature will improve Cordova's
plugin
+ecosystem and reduce some of the frustration that Cordova developers face
when
+adding a new plugin to a project.
+
+<!--more-->
+
+The new API allows for plugin developers to give a mapping of plugin
+releases to project requirements in their `package.json`. When an app
developer
+adds a plugin to their Cordova project, cordova-lib will examine their
+installed plugins, platforms, and cordova-lib version and decide which
+version of the plugin to fetch based on the provided mapping.
+If the project does not fulfill the requirements for the latest release of
the
+plugin, the CLI will print warnings indicating the problems and fetch the
+latest release of the plugin that is compatible.
+
+This API may eventually replace the [engines
element](http://cordova.apache.org/docs/en/latest/plugin_ref/spec.html#engines-and-engine)
in `plugin.xml`.
--- End diff --
I would say it **will** eventually replace the engine element in
plugin.xml! But we can wait until we actually make that change
> Update plugin add behavior to allow plugins to list engine constraints
> ----------------------------------------------------------------------
>
> Key: CB-10679
> URL: https://issues.apache.org/jira/browse/CB-10679
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CordovaLib
> Reporter: Richard B Knoll
> Assignee: Richard B Knoll
> Labels: triaged
>
> Let plugins specify their Cordova related dependencies in their package.json
> so that the CLI can choose a compatible version for the current project.
> Full specification is here:
> https://github.com/cordova/cordova-discuss/pull/30
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
