[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665225#comment-13665225
]
Braden Shepherdson commented on CB-3459:
----------------------------------------
I actually disagree with this. We've already talked about deprecation and the
plugin spec and tools. We agreed they don't have as strict a deprecation policy
as Cordova proper. These tools are not the official path until 3.0, so I'm not
at all convinced they should have logic to support the plugin.xml spec from 2.6
and 2.7, let alone the ancient <plugins-plist> form.
I think supporting these brief misadventures in plugin.xml format is more work
than it's worth when 95% of the new-style plugins that exist are owned by
Cordova developers on this list, who know about the change. Updating all of our
dozen plugins for Chrome-cordova took only a few minutes.
> plugman should handle configuration automatically
> -------------------------------------------------
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Affects Versions: 2.7.0
> Reporter: Anis Kadri
> Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
> <config-file name="config.xml">
> <plugin name="Plugin" value="Plugin" />
> </config-file>
> {code}
> OR
> {code:xml}
> <config-file name="config.xml">
> <feature name="MyPlugin">
> <param name="Plugin" value="Plugin" />
> </feature>
> </config-file>
> {code}
> OR
> {code:xml}
> <plugins-plist key="com.phonegap.plugins.myplugin"
> string="MyPlugin" />
> {code}
--
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
