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

Steve Gill commented on CB-8284:
--------------------------------

Spent some time on this this evening. Debugging the couchapp is not fun. Can't 
wait to move this over to npm. 

I reproduced what you are seeing. Something is wrong and has been since the 
beginning. 

This doesn't prevent us from publishing plugins. When I did a cordova plugin 
add PLUGIN_ID, I got the latest uploaded version of the plugin. 
http://registry.cordova.io/PLUGIN_NAME/-/PLUGIN_NAME-VERSION.tgz definitely 
does not work still. But plugman install is able to grab the plugin from the 
registry. I'd have to look into exactly how this is working. 

Is there a reason we want to be able to download the specific .tgz file? 

Just wondering if it is worth fixing or not. 

> Unable to publish new versions of existing plugins
> --------------------------------------------------
>
>                 Key: CB-8284
>                 URL: https://issues.apache.org/jira/browse/CB-8284
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Registry
>            Reporter: Andrew Grieve
>
> 1. publish a test plugin via `plugman publish .`
> 2. increment plugin.xml version
> 3. publish same test plugin
> Now visit http://registry.cordova.io/PLUGIN_NAME
> Notice the presence of "noattachment":true in the json.
> Now try and download the .tgz for it: 
> http://registry.cordova.io/PLUGIN_NAME/-/PLUGIN_NAME-VERSION.tgz
> And what you get:
> {code}
> {"error":"not_found","reason":"Document is missing attachment"}
> {code}
> I've tested various combinations of unpublish, publish --force, npm 
> --registry=http://registry.cordova.io publish, and get the same result every 
> time. Seems the issue is likely server-side :(.



--
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