You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2015/08/12 04:14:19 UTC
Re: Update: Plugins Registry warnings
"At the last hangout we discussed delaying switching the registry over to
read only until Aug 15thish. We should discuss what else needs to happen
for us to hit this."
This is coming up fast. Anything we need to do before this deadline?
On Thu, Jul 30, 2015 at 10:08 AM, Steven Gill <st...@gmail.com>
wrote:
> So I looked into adding warnings into the registry that users who are
> trying to publish/adduser would get, but it won't work.
>
> If plugman publish is successful, plugman does nothing. If plugman publish
> fails, plugman will output the error that the registry sends.
>
> Once we switch the registry to read-only, I'll add an error message that
> tells users to publish to npm and points them to the appropriate guide.
>
> At the last hangout we discussed delaying switching the registry over to
> read only until Aug 15thish. We should discuss what else needs to happen
> for us to hit this.
>
> The next tools release, plugman looses all commands related to the registry
> (publish, unpublish, adduser, owner). I'll be starting that release right
> after iOS 3.9.0 is done releasing.
>
> I am going to spend time tomorrow trying to gather the emails of people who
> are still publishing and send them an email asking them to move over to
> npm.
>
> -Steve
>
Re: Update: Plugins Registry warnings
Posted by Steven Gill <st...@gmail.com>.
Good call. No redirection yet. Last tools change in regards to CPR was
making it so npm gets hit first and then plugins registry. I will add the
redirection in the next few days (after vlad's merge).
Created an issue: https://issues.apache.org/jira/browse/CB-9589
On Mon, Aug 31, 2015 at 6:29 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> On a related note, was our plan to do re-direction from old plugin
> registry ID to npm ID? I still get a warning and no automatic re-direction
> with latest cordova.
>
> cordova plugin add org.apache.cordova.camera
> Fetching plugin "org.apache.cordova.camera" via npm
> WARNING: org.apache.cordova.camera has been renamed to
> cordova-plugin-camera. You may not be getting the latest version! We
> suggest you `cordova plugin rm org.apache.cordova.camera` and `cordova
> plugin add cordova-plugin-camera`.
>
> Thanks,
> Nikhil
>
>
> -----Original Message-----
> From: Steven Gill [mailto:stevengill97@gmail.com]
> Sent: Monday, August 31, 2015 4:25 PM
> To: dev@cordova.apache.org
> Subject: Re: Update: Plugins Registry warnings
>
> So I have a PR ready to make the registry read-only. [1]
>
> Unfortunately, plugman don't support outputting the errors received from
> the registry to our users. `plugman publish PLUGIN` outputs `publish fail`.
>
> Even though I added a nice error message to the registry, users won't see
> it. Maybe other tools which consume plugins directly from the registry will
> be able to use this message.
>
> If others have better suggestions for this problem, please share.
>
> Any holdback on me merging this commit and deploying it?
>
> Note: I accidentally pushed my original commit to the wrong origin
> (apache) so reverted it.
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-registry%2fpull%2f1&data=01%7c01%7cnikhilkh%40microsoft.com%7cf6adff27b1b24fc2cceb08d2b25b72cb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7PRvSCOB7pl%2b5Hj3MoQAJSOjTWXXBsRluJJ04823hMI%3d
>
> On Tue, Aug 11, 2015 at 7:14 PM, Shazron <sh...@gmail.com> wrote:
>
> > "At the last hangout we discussed delaying switching the registry over
> > to read only until Aug 15thish. We should discuss what else needs to
> > happen for us to hit this."
> >
> > This is coming up fast. Anything we need to do before this deadline?
> >
> > On Thu, Jul 30, 2015 at 10:08 AM, Steven Gill <st...@gmail.com>
> > wrote:
> >
> > > So I looked into adding warnings into the registry that users who
> > > are trying to publish/adduser would get, but it won't work.
> > >
> > > If plugman publish is successful, plugman does nothing. If plugman
> > publish
> > > fails, plugman will output the error that the registry sends.
> > >
> > > Once we switch the registry to read-only, I'll add an error message
> > > that tells users to publish to npm and points them to the appropriate
> guide.
> > >
> > > At the last hangout we discussed delaying switching the registry
> > > over to read only until Aug 15thish. We should discuss what else
> > > needs to happen for us to hit this.
> > >
> > > The next tools release, plugman looses all commands related to the
> > registry
> > > (publish, unpublish, adduser, owner). I'll be starting that release
> > > right after iOS 3.9.0 is done releasing.
> > >
> > > I am going to spend time tomorrow trying to gather the emails of
> > > people
> > who
> > > are still publishing and send them an email asking them to move over
> > > to npm.
> > >
> > > -Steve
> > >
> >
>
RE: Update: Plugins Registry warnings
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
On a related note, was our plan to do re-direction from old plugin registry ID to npm ID? I still get a warning and no automatic re-direction with latest cordova.
cordova plugin add org.apache.cordova.camera
Fetching plugin "org.apache.cordova.camera" via npm
WARNING: org.apache.cordova.camera has been renamed to cordova-plugin-camera. You may not be getting the latest version! We suggest you `cordova plugin rm org.apache.cordova.camera` and `cordova plugin add cordova-plugin-camera`.
Thanks,
Nikhil
-----Original Message-----
From: Steven Gill [mailto:stevengill97@gmail.com]
Sent: Monday, August 31, 2015 4:25 PM
To: dev@cordova.apache.org
Subject: Re: Update: Plugins Registry warnings
So I have a PR ready to make the registry read-only. [1]
Unfortunately, plugman don't support outputting the errors received from the registry to our users. `plugman publish PLUGIN` outputs `publish fail`.
Even though I added a nice error message to the registry, users won't see it. Maybe other tools which consume plugins directly from the registry will be able to use this message.
If others have better suggestions for this problem, please share.
Any holdback on me merging this commit and deploying it?
Note: I accidentally pushed my original commit to the wrong origin (apache) so reverted it.
[1] https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fapache%2fcordova-registry%2fpull%2f1&data=01%7c01%7cnikhilkh%40microsoft.com%7cf6adff27b1b24fc2cceb08d2b25b72cb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7PRvSCOB7pl%2b5Hj3MoQAJSOjTWXXBsRluJJ04823hMI%3d
On Tue, Aug 11, 2015 at 7:14 PM, Shazron <sh...@gmail.com> wrote:
> "At the last hangout we discussed delaying switching the registry over
> to read only until Aug 15thish. We should discuss what else needs to
> happen for us to hit this."
>
> This is coming up fast. Anything we need to do before this deadline?
>
> On Thu, Jul 30, 2015 at 10:08 AM, Steven Gill <st...@gmail.com>
> wrote:
>
> > So I looked into adding warnings into the registry that users who
> > are trying to publish/adduser would get, but it won't work.
> >
> > If plugman publish is successful, plugman does nothing. If plugman
> publish
> > fails, plugman will output the error that the registry sends.
> >
> > Once we switch the registry to read-only, I'll add an error message
> > that tells users to publish to npm and points them to the appropriate guide.
> >
> > At the last hangout we discussed delaying switching the registry
> > over to read only until Aug 15thish. We should discuss what else
> > needs to happen for us to hit this.
> >
> > The next tools release, plugman looses all commands related to the
> registry
> > (publish, unpublish, adduser, owner). I'll be starting that release
> > right after iOS 3.9.0 is done releasing.
> >
> > I am going to spend time tomorrow trying to gather the emails of
> > people
> who
> > are still publishing and send them an email asking them to move over
> > to npm.
> >
> > -Steve
> >
>
Re: Update: Plugins Registry warnings
Posted by Steven Gill <st...@gmail.com>.
So I have a PR ready to make the registry read-only. [1]
Unfortunately, plugman don't support outputting the errors received from
the registry to our users. `plugman publish PLUGIN` outputs `publish fail`.
Even though I added a nice error message to the registry, users won't see
it. Maybe other tools which consume plugins directly from the registry will
be able to use this message.
If others have better suggestions for this problem, please share.
Any holdback on me merging this commit and deploying it?
Note: I accidentally pushed my original commit to the wrong origin (apache)
so reverted it.
[1] https://github.com/apache/cordova-registry/pull/1
On Tue, Aug 11, 2015 at 7:14 PM, Shazron <sh...@gmail.com> wrote:
> "At the last hangout we discussed delaying switching the registry over to
> read only until Aug 15thish. We should discuss what else needs to happen
> for us to hit this."
>
> This is coming up fast. Anything we need to do before this deadline?
>
> On Thu, Jul 30, 2015 at 10:08 AM, Steven Gill <st...@gmail.com>
> wrote:
>
> > So I looked into adding warnings into the registry that users who are
> > trying to publish/adduser would get, but it won't work.
> >
> > If plugman publish is successful, plugman does nothing. If plugman
> publish
> > fails, plugman will output the error that the registry sends.
> >
> > Once we switch the registry to read-only, I'll add an error message that
> > tells users to publish to npm and points them to the appropriate guide.
> >
> > At the last hangout we discussed delaying switching the registry over to
> > read only until Aug 15thish. We should discuss what else needs to happen
> > for us to hit this.
> >
> > The next tools release, plugman looses all commands related to the
> registry
> > (publish, unpublish, adduser, owner). I'll be starting that release right
> > after iOS 3.9.0 is done releasing.
> >
> > I am going to spend time tomorrow trying to gather the emails of people
> who
> > are still publishing and send them an email asking them to move over to
> > npm.
> >
> > -Steve
> >
>