[ 
https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804887#comment-13804887
 ] 

Steve Gill commented on CB-5198:
--------------------------------

Just to add to the discussion, our current master branch is already using the 
registry for dependencies. So this means that people using cordova 3.0 should 
already be facing this problem. Surprised it hasn't been reported. Maybe most 
people have upgraded to 3.1?

Anyways, i suggest this not be a blocker for the plugin release. 

After the release, maybe we spend some time backporting the git ref stuff to 
cordova 3.0?
Then we change the 3.0 docs to download using refs effectively killing our 
reliance on master. Maybe we just add a note on the 3.0.0 docs that they should 
seriously upgrade! I don't know. Thoughts?

> Plugins with dependency's will fail with cordova 3.0
> ----------------------------------------------------
>
>                 Key: CB-5198
>                 URL: https://issues.apache.org/jira/browse/CB-5198
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File Transfer, Plugin Media Capture
>    Affects Versions: 3.0.0
>            Reporter: Steve Gill
>             Fix For: 3.2.0
>
>
> The two plugins above have a dependency tag that downloads from the registry. 
> Cordova 3.0.0 doesn't have support for downloading from the registry. 
> If someone with cordova 3.0.0 installs the file-transfer plugin (using the 
> git url since that was the suggested way for 3.0), it will fail in installing 
> the dependency due to lack of registry support.
> Suggestions
> Bump the major version of these plugins and set engine tag to 3.1.0
> Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from 
> master. Ex. cordova plugin add 
> https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0
>  (I am having trouble with this right now, figuring out why)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to