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

Baptiste Gaillard commented on CB-8490:
---------------------------------------

Hi, please note that this problem seems to be common to all the official Adobe 
Phonegap / Apache Cordova, I created an other issue here : 
http://community.phonegap.com/nitobi/topics/plugins-used-by-phonegap-build-must-be-available-on-the-apache-cordova-registry.


> Phonegap and Cordova registry do not have the save version of the plugin
> ------------------------------------------------------------------------
>
>                 Key: CB-8490
>                 URL: https://issues.apache.org/jira/browse/CB-8490
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin Device
>            Reporter: Baptiste Gaillard
>              Labels: registry
>
> Since few days / weeks it seems version 0.2.x of the plugin is not registered 
> in the Apache Cordova registry (see the JSON payload returned here 
> http://registry.cordova.io/org.apache.cordova.device).
> Because we also use Phonegap Build to build our apps having the same version 
> of plugins available in the Phonegap Build Plugin Registry and the Apache 
> Cordova Publigin registry is required.
> So, the Apache Cordova Registry should provide version 0.2.x of the device 
> plugin. 
> It seems strange to remove old plugin versions from the Apache Cordova 
> Registry because it will break several apps or force developers to upgrade 
> their plugins which is not always advised or necessary. 
> Why do you deleted old plugin versions from the Apache Cordova Registry ? 
> For me a registry MUST keep old versions of packages even if those package 
> are not maintained anymore. 
> Thanks, 
> Baptiste



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to