You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2014/03/04 22:37:47 UTC
Publishing plugins in cordova-plugins
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.
Re: Publishing plugins in cordova-plugins
Posted by Shazron <sh...@gmail.com>.
a) I'm biased, but I think they should be core still :P
b) that assumes someone wants to take the sole responsibility of this on
c) not sure
d) why not? it's still a plugin
On Tue, Mar 4, 2014 at 1:37 PM, Andrew Grieve <ag...@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.
>
Re: Publishing plugins in cordova-plugins
Posted by Brian LeRoux <b...@brian.io>.
Feel that statusbar is popular enough that it should be considered core.
Feel that keyboard and file-system-root are both worthy of first class
support too.
In favor of just adding/graduating them to the whole /dist publishing
policy.
On Tue, Mar 4, 2014 at 1:37 PM, Andrew Grieve <ag...@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.
>
Re: Publishing plugins in cordova-plugins
Posted by Andrew Grieve <ag...@chromium.org>.
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 <sh...@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 <ag...@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.
> >
>
Re: Publishing plugins in cordova-plugins
Posted by Shazron <sh...@gmail.com>.
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 <ag...@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.
>
Re: Publishing plugins in cordova-plugins
Posted by Shazron <sh...@gmail.com>.
I'll get the threads going
On Wed, Mar 5, 2014 at 9:43 AM, Michal Mocny <mm...@chromium.org> wrote:
> We discussed this at the Face to Face yesterday (maybe that prompted this
> mail?).
>
> I'm +1 for statusbar (as was everyone), but I'm -0 on keyboard (won't block
> it, but I don't like it), since its really buggy as-is, and its benefits
> come with real tradeoffs. Additionally, I don't think is enough support
> for maintaining it from the core contributors at the moment (I may be
> wrong).
>
> Either way, lets spin up dedicated threads for these requests so we can
> discuss specifically.
>
>
> On Tue, Mar 4, 2014 at 8:57 PM, luoq <lu...@polyvi.com> wrote:
>
> > Hi,
> >
> > I believe the statusbar & keyboard at least should be promoted to common
> > core plugins ASAP, it's a MUST for iOS7.
> >
> > Thanks.
> >
> >
> > --
> > Best Regards,
> > Qi LUO
> > Sent with Air
> >
> > On 5 March, 2014 at 5:45:18, Andrew (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.
> >
>
Re: Publishing plugins in cordova-plugins
Posted by Michal Mocny <mm...@chromium.org>.
We discussed this at the Face to Face yesterday (maybe that prompted this
mail?).
I'm +1 for statusbar (as was everyone), but I'm -0 on keyboard (won't block
it, but I don't like it), since its really buggy as-is, and its benefits
come with real tradeoffs. Additionally, I don't think is enough support
for maintaining it from the core contributors at the moment (I may be
wrong).
Either way, lets spin up dedicated threads for these requests so we can
discuss specifically.
On Tue, Mar 4, 2014 at 8:57 PM, luoq <lu...@polyvi.com> wrote:
> Hi,
>
> I believe the statusbar & keyboard at least should be promoted to common
> core plugins ASAP, it's a MUST for iOS7.
>
> Thanks.
>
>
> —
> Best Regards,
> Qi LUO
> Sent with Air
>
> On 5 March, 2014 at 5:45:18, Andrew (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.
>
Re: Adding platform Firfoxos fails
Posted by Piotr Zalewa <pz...@mozilla.com>.
Before it gets to production, a quick and dirty solution is to downgrade
cordova to a 3.4.0-0.1.0 version. I've got no idea how it affects apps
or other platforms.
npm install cordova@3.4.0-0.1.0 -g
Piotr
On 03/07/2014 11:53 PM, James Long wrote:
> Thanks for telling us about the issue. I can reproduce the error
> locally and there's already a PR on the repo to fix it. I also filed
> the issue in jira here: https://issues.apache.org/jira/browse/CB-6200
>
> Please watch that issue. We should be able to fix this quickly.
>
> On Wed, Mar 5, 2014 at 1:27 PM, Gert-Jan Braas <br...@steckelfisch.nl> wrote:
>> Stacktrace:
>> ==============================
>> braas@chickenrun:~/projects/ligplekkenonderweg/LPOWC$ cordova platform add
>> firefoxos
>> Creating firefoxos project...
>> Creating Firefox OS project
>> Project Path
>> ../../../../../../home/braas/projects/ligplekkenonderweg/LPOWC/platforms/firefoxos
>> Package Name lpow.steckelfisch.nl
>> Project Name LigplekkenOnderweg
>> Installing org.apache.cordova.core.dialogs (firefoxos)
>> ReferenceError: xml_helpers is not defined
>> at Object.module.exports.package_name
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/platforms/firefoxos.js:25:26)
>> at PlatformMunger.generate_plugin_config_munge
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:285:54)
>> at PlatformMunger.add_plugin_changes
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:211:29)
>> at
>> /var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:368:14
>> at Array.forEach (native)
>> at PlatformMunger_process [as process]
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:367:45)
>> at Object.exports.process
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:77:12)
>> at Object.handlePrepare
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/prepare.js:74:20)
>> at
>> /var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/install.js:420:33
>> at _fulfilled
>> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/node_modules/q/q.js:798:54)
>> --
>>
>> Created issue CB-6160 (https://issues.apache.org/jira/browse/CB-6160)
>>
>> and pull request https://github.com/apache/cordova-plugman/pull/61
>>
>>
>>
>> ====================
>> U ademt. Dat hebben wij gepatenteerd.
>> Mogen we even vangen?
>> -------------------------------------
>>
--
Piotr Zalewa
Mozilla
Re: Adding platform Firfoxos fails
Posted by James Long <jl...@mozilla.com>.
Thanks for telling us about the issue. I can reproduce the error
locally and there's already a PR on the repo to fix it. I also filed
the issue in jira here: https://issues.apache.org/jira/browse/CB-6200
Please watch that issue. We should be able to fix this quickly.
On Wed, Mar 5, 2014 at 1:27 PM, Gert-Jan Braas <br...@steckelfisch.nl> wrote:
> Stacktrace:
> ==============================
> braas@chickenrun:~/projects/ligplekkenonderweg/LPOWC$ cordova platform add
> firefoxos
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path
> ../../../../../../home/braas/projects/ligplekkenonderweg/LPOWC/platforms/firefoxos
> Package Name lpow.steckelfisch.nl
> Project Name LigplekkenOnderweg
> Installing org.apache.cordova.core.dialogs (firefoxos)
> ReferenceError: xml_helpers is not defined
> at Object.module.exports.package_name
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/platforms/firefoxos.js:25:26)
> at PlatformMunger.generate_plugin_config_munge
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:285:54)
> at PlatformMunger.add_plugin_changes
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:211:29)
> at
> /var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:368:14
> at Array.forEach (native)
> at PlatformMunger_process [as process]
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:367:45)
> at Object.exports.process
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:77:12)
> at Object.handlePrepare
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/prepare.js:74:20)
> at
> /var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/install.js:420:33
> at _fulfilled
> (/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/node_modules/q/q.js:798:54)
> --
>
> Created issue CB-6160 (https://issues.apache.org/jira/browse/CB-6160)
>
> and pull request https://github.com/apache/cordova-plugman/pull/61
>
>
>
> ====================
> U ademt. Dat hebben wij gepatenteerd.
> Mogen we even vangen?
> -------------------------------------
>
Adding platform Firfoxos fails
Posted by Gert-Jan Braas <br...@steckelfisch.nl>.
Stacktrace:
==============================
braas@chickenrun:~/projects/ligplekkenonderweg/LPOWC$ cordova platform
add firefoxos
Creating firefoxos project...
Creating Firefox OS project
Project Path
../../../../../../home/braas/projects/ligplekkenonderweg/LPOWC/platforms/firefoxos
Package Name lpow.steckelfisch.nl
Project Name LigplekkenOnderweg
Installing org.apache.cordova.core.dialogs (firefoxos)
ReferenceError: xml_helpers is not defined
at Object.module.exports.package_name
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/platforms/firefoxos.js:25:26)
at PlatformMunger.generate_plugin_config_munge
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:285:54)
at PlatformMunger.add_plugin_changes
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:211:29)
at
/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:368:14
at Array.forEach (native)
at PlatformMunger_process [as process]
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:367:45)
at Object.exports.process
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/util/config-changes.js:77:12)
at Object.handlePrepare
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/prepare.js:74:20)
at
/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/src/install.js:420:33
at _fulfilled
(/var/tmp/braas/projects/cordova/cordova-apachegit/cordova-plugman/node_modules/q/q.js:798:54)
--
Created issue CB-6160 (https://issues.apache.org/jira/browse/CB-6160)
and pull request https://github.com/apache/cordova-plugman/pull/61
====================
U ademt. Dat hebben wij gepatenteerd.
Mogen we even vangen?
-------------------------------------
Re: Publishing plugins in cordova-plugins
Posted by luoq <lu...@polyvi.com>.
Hi,
I believe the statusbar & keyboard at least should be promoted to common core plugins ASAP, it's a MUST for iOS7.
Thanks.
—
Best Regards,
Qi LUO
Sent with Air
On 5 March, 2014 at 5:45:18, Andrew (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.