Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AED1E17216 for ; Wed, 29 Oct 2014 22:06:05 +0000 (UTC) Received: (qmail 16512 invoked by uid 500); 29 Oct 2014 22:06:05 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 16470 invoked by uid 500); 29 Oct 2014 22:06:05 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 16457 invoked by uid 99); 29 Oct 2014 22:06:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2014 22:06:04 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jwargo23@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2014 22:05:39 +0000 Received: by mail-qc0-f171.google.com with SMTP id m20so3294793qcx.30 for ; Wed, 29 Oct 2014 15:05:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=ujucGmJeeJnZg4BukqVnhx5+MWQkRcQRQkZrzrI6SV8=; b=EyG527/iD3WHN6iZ42PsI1DVDZenXUov2vbhkDsE+prr95UX7ktJbudxv2PoAKwayy 0z9aH56fOEQ1ekBL4BwFGnO42u5aUzBQu0gvhcaK5nqeHsfo/8h9JokOWuT4Gqd4cStD aGjPtw5XnKp2ecP8ZDs8//m40uQNReT7wYU8dzdJk06BhBnAWojqDvM4zDyrevlQqV9N 88da2qXXF7hKuG+DZG2NsL41PmJYlhCGhzIn3r7PuXYAgdfDaUJjYqeisW4rJMr1WtN2 FLLWp/5fOE46Ggm35eV9JeRBQjPdwUjr4on8kMHk5fyhBG6V0LGypQFDEnBimEfyVZWA OO9Q== X-Received: by 10.224.66.200 with SMTP id o8mr20716286qai.88.1414620337957; Wed, 29 Oct 2014 15:05:37 -0700 (PDT) Received: from [127.0.0.1] (cpe-075-181-098-190.carolina.res.rr.com. [75.181.98.190]) by mx.google.com with ESMTPSA id s10sm5239754qac.14.2014.10.29.15.05.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Oct 2014 15:05:37 -0700 (PDT) Message-ID: <545164AB.4060904@gmail.com> Date: Wed, 29 Oct 2014 18:05:31 -0400 From: "John M. Wargo" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev@cordova.apache.org Subject: Re: Plugman issues/questions References: <5450E320.4000809@gmail.com> <54515108.1060207@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060600090806040503020306" X-Virus-Checked: Checked by ClamAV on apache.org --------------060600090806040503020306 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Shaz, Thanks. I just tried it against my registry entry and was able to get it to work. There's a bug in plugman - if I don't provide a plugin ID, I get weird errors. For example, if I issue "plugman owner ls" and don't provide a plugin ID, I get a 404 error rather than something like "You did't provide a plugin name" I'll create a ticket. On 10/29/2014 5:04 PM, Shazron wrote: > ``` > $ plugman owner ls org.apache.cordova.core.file > $ plugman owner add username org.apache.cordova.core.file > $ plugman owner rm username org.apache.cordova.core.file > ``` > > plugins.cordova.io basically uses npm code on the backend, so it's similar > (substitute package for plugin). Each plugin on plugins.cordova.io has > owners -- i.e. people that have permissions to publish updates to the > plugin, "ls" here lists all owners (and their emails). Similarly "add" and > "rm" removes owners for each plugin. > > On Wed, Oct 29, 2014 at 1:41 PM, John M. Wargo wrote: > >> Steve, >> >> I'd love to make the changes, but I can't right now. With my day job and >> trying to finish up Apache Cordova 4 Programming at night, I won't be able >> to contribute any doc changes until after that is done. >> >> Yeah, I figured as much, but the download link on the home page says >> "Download 4.0" and there isn't one. So someone following the plugman and >> platform docs will be confused. >> >> [1] doesn't have information about owner, all it says is: >> >> $ plugman owner ls org.apache.cordova.core.file >> $ plugman owner add username org.apache.cordova.core.file >> $ plugman owner rm username org.apache.cordova.core.file >> >> Which doesn't tell anything about what it means, what it's supposed to do >> and how it's supposed to work (sorry). when I execute an ls, I get an >> error. For the other ones, what am I adding and removing? a Plugin >> Repository user name? Npm user name? Just a name? There's no details, no >> examples, nothing. so I don't understand how I'm supposed to understand how >> to use this without any information except for the commands. Where does >> owner write the information? The config.xml? somewhere else? Does this go >> to the registry? See what I mean? >> >> Any chance you can provide me with a little background you have on owner? >> >> I'll submit a ticket for unpublish. >> >> >> On 10/29/2014 2:40 PM, Steven Gill wrote: >> >>> Hey John, >>> >>> Thanks for filing the two issues. It would be great if you could send PRs >>> for them too! I believe the correct information is in this help file [1] >>> >>> Platform scripts: the platforms were not bumped to version 4.0. What you >>> see at https://www.apache.org/dist/cordova/platforms/ is the latest >>> released platforms. 4.0.0 referes to the cordova cli version. You can read >>> more about our change in versioning at >>> http://cordova.apache.org/announcements/2014/10/16/cordova-4.html >>> >>> [1] also has info on addUser and owner. This info needs to be copied over >>> to docs.cordova.io. Would love some help with that if you have time! >>> >>> You should not be creating a package.json. plugman publish command will >>> create one based on values from your plugin.xml. It gets deleted after a >>> successful publish. >>> >>> Plugman unpublish might be a bug. File it. >>> >>> Checkout a existing plugins plugin.xml [2] to see how we set description, >>> repo, keywords, etc. If you have a README.md file, that will also get >>> uploaded on publish. >>> >>> We don't have any login setup on the site. We have an existing issue at >>> [3]. Just no time to do it. >>> >>> As you can see, our documentation around plugin publishing is severely >>> lacking. We could really use some help sprucing it up! >>> >>> [1] https://github.com/apache/cordova-plugman/blob/master/doc/help.txt >>> [2] https://github.com/apache/cordova-plugin-file/blob/master/plugin.xml >>> [3] https://issues.apache.org/jira/browse/CB-7246 >>> >>> >>> >>> On Wed, Oct 29, 2014 at 10:43 AM, Brian LeRoux wrote: >>> >>> thats def a bug John / pls file! >>>> On Wed, Oct 29, 2014 at 5:52 AM, John M. Wargo >>>> wrote: >>>> >>>> I'm playing around with plugman in Cordova 4.0 and have found some >>>>> issues >>>>> and have some questions. >>>>> >>>>> First of all, the docs are incorrect and I've filed a ticket: >>>>> https://issues.apache.org/jira/browse/CB-7894. The example for adding >>>>> a >>>>> plugin is missing the install switch.: >>>>> >>>>> $ plugman -platform >>>>> --project --plugin [--plugins_dir >>>>> >>>> ] >>>> >>>>> [--www ] [-variable = [--variable = >>>>> ...]] >>>>> >>>>> It should be: >>>>> >>>>> $ plugman install -platform >>>> blackberry10|wp8> >>>>> --project --plugin [--plugins_dir >>>>> ] >>>>> [--www ] [-variable = [--variable = >>>>> ...]] >>>>> >>>>> The docs also say that the switch for uninstall is "--uninstall", but in >>>>> my testing it's actually "uninstall" - I've created a ticket for this: >>>>> https://issues.apache.org/jira/browse/CB-7895. >>>>> >>>>> The docs say to use the platform scripts to create a plugman project, >>>>> but >>>>> when I follow the links to the download, there's no download for Cordova >>>>> 4.0. When will that be published? >>>>> >>>>> When I unpublish my plugin, it says it's unpublished, but the entry is >>>>> still there in the registry. Should I submit a ticket for this? >>>>> >>>>> I can't find any information on what the plugman owner command does. >>>>> When >>>>> I execute it, I get an error: >>>>> >>>>> C:\Users\jwargo\dev\myplugin>plugman owner ls >>>>> ENOENT, open 'C:\Users\jwargo\dev\myplugin\package.json' >>>>> >>>>> I can't find anything in the docs that tells me I should be creating a >>>>> package.json. Should I be? >>>>> >>>>> I created one using npm init. Then, when I issue a plugman owner ls I >>>>> get >>>>> the following error: >>>>> >>>>> 404 Not Found: myplugin >>>>> >>>>> Can someone explain to me how this is supposed to work? I can't seem to >>>>> find any documentation on this command. >>>>> >>>>> Regarding the registry, it doesn't explain anywhere how to set the >>>>> description for the plugin - I'm assuming it's through a readme.md >>>>> file. >>>>> I also don't see anywhere I can login to the registry site and edit my >>>>> entry. I'm assuming also that keywords are set through the package.json >>>>> file? >>>>> >>>>> -- >>>>> John M. Wargo >>>>> @johnwargo >>>>> www.johnwargo.com >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------------------------------------ >>>>> ------------------------------ >>>>> >>>>> >>>>> --------------060600090806040503020306--