cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anis KADRI <>
Subject Re: About plugins in 3.1
Date Tue, 17 Sep 2013 20:30:33 GMT
$ cordova plugin add # cuz we decided
to use package names for IDs to avoid collisions

Yes, it would take the latest version but you can specify which
version you want by running

$ cordova plugin add

On Tue, Sep 17, 2013 at 1:25 PM, Steven Gill <> wrote:
> What would the command look like to install it if we aren't using git urls?
> cordova plugin add camera? Would it automatically take the latest version
> off the registery?
> I like the idea of working on master and tagging a plugin when it is ready
> to be published.
> On Tue, Sep 17, 2013 at 1:21 PM, Anis KADRI <> wrote:
>> As far as I understand and following this documentation:
>> Plugins are currently fetched using git from origin/master. It is a
>> major problem in my opinion. The main reason (but there are many) is
>> that any commit to master can potentially break plugins. Yes, we can
>> do a dev branch but some people are forgetful and might commit to
>> master anyway. I think the proper development process for plugins
>> should be:
>> - Always commit to master
>> - When you're ready to release a plugin: update the version, tag it
>> and publish it to the cordova registry.
>> - Users can then install the latest version without having to remember
>> a git URL and without worrying about getting a broken plugin.
>> Ideally, every Cordova committer should be granted the right to
>> publish to the registry. Right now, I've only added Andrew Grieve (who
>> is having issues publishing atm...). If anybody wants to be added, let
>> me know.
>> Does that sound good to everyone?
>> -a

View raw message