Sure, cordova-plugman is here [1]
cordova-cli is here [2] the registry itself is here [3] and the website to browse plugins is here [4] [1] http://bit.ly/1bKTvsd [2] http://bit.ly/1bKTHYu [3] http://registry.cordova.io [4] http://plugins.cordova.io It's easy to setup your own registry and it's also easy to replicate from one registry to the other. -a On Tue, Jul 23, 2013 at 4:41 PM, Steven Gill <stevengil...@gmail.com> wrote: > Hey Anis, > > Sounds awesome! Can you share the repo links for the registry itself and > any other repos that are related? > > > On Tue, Jul 23, 2013 at 4:26 PM, Anis KADRI <a...@apache.org> wrote: > > > Hello, > > > > I wanted to update the list on my progress on this topic. I've been > working > > on this for the past month or so and I believe it will solve the issue of > > finding plugins for our users (core and 3rd party). > > > > I committed everything to plugman and cordova-cli under the > > 'plugman-registry' > > > > Everything should be well documented under the project's README but I > > should probably update the wiki and write a blog post as well. > > > > Now that 3.0 is released, I would like to merge this feature back into > > master on both projects by the end of this week if possible. It would be > > great if folks try it out and give me some feedback. > > > > The registry is based on NPM and because of that, all of your plugins > need > > to be renamed using NPM's conventions: all lowercase and no spaces. I've > > already published some to plugins.cordova.io. > > > > plugman allows to install, adduser, publish, unpublish and search. > > cordova-cli only allows installation and search. I think that plugin > > authoring should be done with plugman as I am not sure what the flow > would > > look like with cordova-cli. This can change. > > > > The only difference between npm and plugman is the (un)installation part. > > Everything else is pretty much the same. Plugin authors are not required > to > > write a package.json as this is automatically generated by the tool from > > the plugin.xml. I've added a few tags to the specification to support > this > > new use case. > > > > Let me know if you have any questions or requests. > > > > Anis > > >
