[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673344#comment-13673344
]
Braden Shepherdson commented on CB-3459:
We have tags to describe what versions of Cordova something supports.
I don't think we should be doing extra work to make these tools - which are not
really released until 3.0 anyway - backward compatible, especially with Cordova
versions ancient enough to still have . That's way outside the
deprecation window, now.
> 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}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> 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
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
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}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> 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
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665420#comment-13665420
]
Braden Shepherdson commented on CB-3459:
Let's distinguish between changes that break the tools for plugin developers,
and changes that break the tools for application developers. This is the former
- it only matters if you're maintaining a plugin.xml somewhere. For that, I
think yes, we can break backwards compatibility in this not-yet-really-released
tools.
We seem to have fallen into the trap of "release early, discover when you try
to release often that people depend on your alpha crap you're trying to fix."
These tools should have had a nice big "alpha, under heavy development, expect
suffering" warning label on them from the beginning, that we removed with 3.0
and their official launch.
Now we're looking at the npm downloads and worrying about breaking things, with
tools that have evolved massively in the last few weeks already, quite apart
from this change. Plugin authors will have to update eventually - how much work
are we prepared to do to buy them two months of wiggle room for a 90-second
change to their plugin.xml files?
> 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}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> 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
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665406#comment-13665406
]
Anis Kadri commented on CB-3459:
You are essentially saying that we should break backwards compatibility and
only target Cordova 3.0 ?
> 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}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> 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
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
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 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}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> 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
