cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Publishing plugins in cordova-plugins
Date Wed, 05 Mar 2014 19:18:48 GMT
There is now a client-side whitelist of plugins that can be published under
org.apache.cordova.* It lives at plugman/src/registry/whitelist.js.


On Tue, Mar 4, 2014 at 5:48 PM, Shazron <shazron@gmail.com> wrote:

> Of course now with the latest plugman I can't publish statusbar:
> "Invalid Plugin ID. The "org.apache.cordova" prefix is reserved for plugins
> provided directly by the Cordova project."
>
> How do I publish with that namespace?
>
>
> On Tue, Mar 4, 2014 at 1:37 PM, Andrew Grieve <agrieve@chromium.org>
> wrote:
>
> > statusbar and keyboard are published already.
> >
> > I *think* Shaz was having trouble updating them though? (and I think I
> > fixed the bug in plugman just yesterday).
> >
> > Noticed that they fail the whitelist check in plugman, so with a recent
> > version of plugman you wouldn't be able to publish them.
> >
> > And... Since these plugins are somewhat experimental and we're starting
> the
> > process of voting and publishing plugins to dist/, I wonder:
> >
> > a) Should we change the ID of these plugins to, say
> > "org.apache.cordova.labs"
> > b) Should we move these plugins to github and have them not under apache
> > for now, e.g.: com.shazron.statusbar
> > c) Should we just add them to the plugin release process.
> > d) Should we just never publish them to the registry and have people use
> > them via git url.
> >
> > What do people think?
> >
> > Current motive is that I would like file-system-roots to be published.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message