[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665687#comment-13665687
]
Anis Kadri commented on CB-3459:
--------------------------------
Actually, forcing plugin developers to update their spec is not a big issue
because as you mentioned the spec has changed and might change again before
3.0. Worst-case scenario we can do it for them.
Nevertheless, should a plugin that uses the latest spec be backward compatible
with previous Cordova versions? What do you think of that use-case ? I
personally think it should.
> 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}
> OR better yet
> Have the latest plugin.xml spec support old Cordova versions (plist, new/old
> xml).
--
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
