Re: No Readme for plugin packages on npm
I filed the issue a few days ago with npm. They are working on fixing it. The parser is struggling with html comments On Apr 23, 2015 6:14 PM, "Nikhil Khandelwal" wrote: > It looks like npm cannot find the readme for plugin packages: > https://www.npmjs.com/package/cordova-plugin-battery-status > > Github can find it just fine though: > https://github.com/apache/cordova-plugin-battery-status > > Thanks, > Nikhil >
[GitHub] cordova-docs pull request: CB-8794 Update links to plugins to poin...
GitHub user nikhilkh opened a pull request: https://github.com/apache/cordova-docs/pull/281 CB-8794 Update links to plugins to point to npm. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs plugin_links Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/281.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #281 commit 811dfa78bf8dbc981f6019916238bf6c8906752f Author: Nikhil Khandelwal Date: 2015-04-24T01:19:25Z CB-8794 Update links to plugins to point to npm. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
No Readme for plugin packages on npm
It looks like npm cannot find the readme for plugin packages: https://www.npmjs.com/package/cordova-plugin-battery-status Github can find it just fine though: https://github.com/apache/cordova-plugin-battery-status Thanks, Nikhil
Re: [DISCUSS] Docs release
Cool! I'm working on translations right now 2015-04-23 19:22 GMT-05:00 Steven Gill : > 5.0.0 for docs has been published. We can update it again later once we > have translations ready to go. > > http://docs.cordova.io > > On Thu, Apr 23, 2015 at 2:50 PM, Victor Sosa > wrote: > > > Hi Andrey. > > As we chatted on Hangout, I'll update the Russian docs but it'll take > some > > time, please be patient. > > > > @Steven: I'll check those changes in other languages (as much as I can) > > > > 2015-04-23 13:19 GMT-05:00 Steven Gill : > > > > > I changed all references to org.apache.cordova.* to cordova-plugin-*. > > Docs > > > look good to publish I think. > > > > > > On Wed, Apr 22, 2015 at 8:31 PM, Andrey Kurdumov < > > kant2...@googlemail.com> > > > wrote: > > > > > > > Could Viktor or Lisa update all untranslated Russian in CrowdIn. > > > > If I understand correclty, they could just use Microsoft translator > for > > > > that and do that automatically. > > > > I have to do that manually, and I don't have cycles to fully > > > > translate/proofread language for this release. > > > > > > > > 2015-04-22 7:43 GMT+06:00 Sergey Grebnov (Akvelon) < > > > v-seg...@microsoft.com > > > > >: > > > > > > > > > I've sent a PR to update platform guides as per discussion in a > > > separate > > > > > thread; it will be great if we can review and include it to docs > > > release > > > > > > > > > > https://github.com/apache/cordova-docs/pull/279 > > > > > > > > > > Thx! > > > > > Sergey > > > > > -Original Message- > > > > > From: Steven Gill [mailto:stevengil...@gmail.com] > > > > > Sent: Tuesday, April 21, 2015 5:49 PM > > > > > To: dev@cordova.apache.org > > > > > Subject: [DISCUSS] Docs release > > > > > > > > > > I'm going to look into doing this. Any blockers, let me know > > > > > > > > > > Don't believe we have to vote on this one. > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Victor Adrian Sosa Herrera > > IBM Software Engineer > > Guadalajara, Jalisco > > > -- Victor Adrian Sosa Herrera IBM Software Engineer Guadalajara, Jalisco
Re: [DISCUSS] Docs release
5.0.0 for docs has been published. We can update it again later once we have translations ready to go. http://docs.cordova.io On Thu, Apr 23, 2015 at 2:50 PM, Victor Sosa wrote: > Hi Andrey. > As we chatted on Hangout, I'll update the Russian docs but it'll take some > time, please be patient. > > @Steven: I'll check those changes in other languages (as much as I can) > > 2015-04-23 13:19 GMT-05:00 Steven Gill : > > > I changed all references to org.apache.cordova.* to cordova-plugin-*. > Docs > > look good to publish I think. > > > > On Wed, Apr 22, 2015 at 8:31 PM, Andrey Kurdumov < > kant2...@googlemail.com> > > wrote: > > > > > Could Viktor or Lisa update all untranslated Russian in CrowdIn. > > > If I understand correclty, they could just use Microsoft translator for > > > that and do that automatically. > > > I have to do that manually, and I don't have cycles to fully > > > translate/proofread language for this release. > > > > > > 2015-04-22 7:43 GMT+06:00 Sergey Grebnov (Akvelon) < > > v-seg...@microsoft.com > > > >: > > > > > > > I've sent a PR to update platform guides as per discussion in a > > separate > > > > thread; it will be great if we can review and include it to docs > > release > > > > > > > > https://github.com/apache/cordova-docs/pull/279 > > > > > > > > Thx! > > > > Sergey > > > > -Original Message- > > > > From: Steven Gill [mailto:stevengil...@gmail.com] > > > > Sent: Tuesday, April 21, 2015 5:49 PM > > > > To: dev@cordova.apache.org > > > > Subject: [DISCUSS] Docs release > > > > > > > > I'm going to look into doing this. Any blockers, let me know > > > > > > > > Don't believe we have to vote on this one. > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > > > > > -- > Victor Adrian Sosa Herrera > IBM Software Engineer > Guadalajara, Jalisco >
[GitHub] cordova-docs pull request: CB-8485 Documenting the support to sign...
GitHub user nikhilkh opened a pull request: https://github.com/apache/cordova-docs/pull/280 CB-8485 Documenting the support to sign iOS app This feature is not part of the TOOLS 5.0 release and should not be merged before that DOCS release. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs ios_sign Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/280.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #280 commit 543fb95e5db8fa772e8fc946828206ebd929d0a9 Author: Nikhil Khandelwal Date: 2015-04-23T22:00:16Z CB-8485 Documenting the support to sign iOS app --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-whitelist pull request: Fixed error in Content-Secu...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-whitelist/pull/3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-whitelist pull request: Just a typo (*h*avigation)
Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-whitelist/pull/4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: Update elementtree dependency to 0.1.6. ...
GitHub user shazron opened a pull request: https://github.com/apache/cordova-lib/pull/209 Update elementtree dependency to 0.1.6. Note it has a breaking API chang... ...e. https://github.com/racker/node-elementtree/issues/24 You can merge this pull request into a Git repository by running: $ git pull https://github.com/shazron/cordova-lib elementtree-0.1.6-update Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/209.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #209 commit 60ea35ea0b1df9c2a0d59af6f817fc45941036c3 Author: Shazron Abdullah Date: 2015-04-23T23:55:40Z Update elementtree dependency to 0.1.6. Note it has a breaking API change. https://github.com/racker/node-elementtree/issues/24 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-whitelist pull request: Just a typo (*h*avigation)
GitHub user aabluedragon opened a pull request: https://github.com/apache/cordova-plugin-whitelist/pull/4 Just a typo (*h*avigation) You can merge this pull request into a Git repository by running: $ git pull https://github.com/aabluedragon/cordova-plugin-whitelist patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-whitelist/pull/4.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4 commit 73f95ef8d37aebb309a41ac2e4e4f0e4a6d927a2 Author: aabluedragon Date: 2015-04-23T23:25:33Z Just a typo (*h*avigation) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Buildbot: buildslave cordova-ios-slave was lost
No worries, glad you're on it! @purplecabbage risingj.com On Thu, Apr 23, 2015 at 3:49 PM, Dmitry Blotsky wrote: > Yep. Turns out it was falling asleep. I recently wiped the machine and > forgot to uncheck the "Fall asleep sometimes" option. That was silly. Sorry > about that. > > -Original Message- > From: Jesse [mailto:purplecabb...@gmail.com] > Sent: Thursday, April 23, 2015 3:43 PM > To: dev@cordova.apache.org > Subject: Re: Buildbot: buildslave cordova-ios-slave was lost > > Thanks Dmitry! > > oh no! It happened again! > > @purplecabbage > risingj.com > > On Thu, Apr 23, 2015 at 3:10 PM, Dmitry Blotsky > wrote: > > > OSX slave went down because it lost contact with the master for some > > reason. Back up now. > > > > -Original Message- > > From: build...@apache.org [mailto:build...@apache.org] > > Sent: Thursday, April 23, 2015 2:37 PM > > To: dev@cordova.apache.org > > Subject: Buildbot: buildslave cordova-ios-slave was lost > > > > The Buildbot working for 'ASF Buildbot' > > has noticed that the buildslave named cordova-ios-slave went away > > > > It last disconnected at Thu Apr 23 21:31:41 2015 (buildmaster-local > > time) > > > > The admin on record (as reported by BUILDSLAVE:info/admin) was 'Your > > Name Here '. > > > > Sincerely, > > The Buildbot > > http://ci.apache.org/ > > > > http://ci.apache.org/buildslaves/cordova-ios-slave > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
RE: Buildbot: buildslave cordova-ios-slave was lost
Yep. Turns out it was falling asleep. I recently wiped the machine and forgot to uncheck the "Fall asleep sometimes" option. That was silly. Sorry about that. -Original Message- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Thursday, April 23, 2015 3:43 PM To: dev@cordova.apache.org Subject: Re: Buildbot: buildslave cordova-ios-slave was lost Thanks Dmitry! oh no! It happened again! @purplecabbage risingj.com On Thu, Apr 23, 2015 at 3:10 PM, Dmitry Blotsky wrote: > OSX slave went down because it lost contact with the master for some > reason. Back up now. > > -Original Message- > From: build...@apache.org [mailto:build...@apache.org] > Sent: Thursday, April 23, 2015 2:37 PM > To: dev@cordova.apache.org > Subject: Buildbot: buildslave cordova-ios-slave was lost > > The Buildbot working for 'ASF Buildbot' > has noticed that the buildslave named cordova-ios-slave went away > > It last disconnected at Thu Apr 23 21:31:41 2015 (buildmaster-local > time) > > The admin on record (as reported by BUILDSLAVE:info/admin) was 'Your > Name Here '. > > Sincerely, > The Buildbot > http://ci.apache.org/ > > http://ci.apache.org/buildslaves/cordova-ios-slave > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: Buildbot: buildslave cordova-ios-slave was lost
Thanks Dmitry! oh no! It happened again! @purplecabbage risingj.com On Thu, Apr 23, 2015 at 3:10 PM, Dmitry Blotsky wrote: > OSX slave went down because it lost contact with the master for some > reason. Back up now. > > -Original Message- > From: build...@apache.org [mailto:build...@apache.org] > Sent: Thursday, April 23, 2015 2:37 PM > To: dev@cordova.apache.org > Subject: Buildbot: buildslave cordova-ios-slave was lost > > The Buildbot working for 'ASF Buildbot' > has noticed that the buildslave named cordova-ios-slave went away > > It last disconnected at Thu Apr 23 21:31:41 2015 (buildmaster-local time) > > The admin on record (as reported by BUILDSLAVE:info/admin) was 'Your Name > Here '. > > Sincerely, > The Buildbot > http://ci.apache.org/ > > http://ci.apache.org/buildslaves/cordova-ios-slave > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Buildbot: buildslave cordova-ios-slave was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named cordova-ios-slave went away It last disconnected at Thu Apr 23 22:31:19 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Dmitry Blotsky '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/cordova-ios-slave - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-splashscreen pull request: Add fullscreen options
GitHub user TheBosZ opened a pull request: https://github.com/apache/cordova-plugin-splashscreen/pull/45 Add fullscreen options This change adds settings to hide the navigation and status bars while the splash screen is displayed. Full-screen apps aren't affected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/TheBosZ/cordova-plugin-splashscreen add-fullscreen-options Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-splashscreen/pull/45.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #45 commit 5969cfae37beab6944b768b16365d011055d9991 Author: Nathan Kerr Date: 2015-03-11T16:32:29Z Hide nav bar while showing splash screen commit 891cbf29bf0a7194f637fac4987c1ff4da97f146 Author: Nathan Kerr Date: 2015-03-11T17:32:40Z Hide status bar as well commit dc5e8ea5aa2d83fe510f7be286455f97adbee3f7 Author: Nathan Kerr Date: 2015-04-23T20:55:44Z Merge remote-tracking branch 'cordova/master' into add-fullscreen-options commit 2cd8e1affdadc238c56dffa085e80b93c8b9bd0c Author: Nathan Kerr Date: 2015-04-23T20:56:55Z Make the fullscreen settings be options commit 1d47ba4b2a9579e48240c8db530b8aef67ef7c6f Author: Nathan Kerr Date: 2015-04-23T21:03:33Z Fix syntax error commit 4f0a3f2d0e088acd830b90a662f54a0d243f3d7a Author: Nathan Kerr Date: 2015-04-23T22:12:42Z Documentation and namespace the preferences to match the other ones --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Buildbot: buildslave cordova-ios-slave was lost
OSX slave went down because it lost contact with the master for some reason. Back up now. -Original Message- From: build...@apache.org [mailto:build...@apache.org] Sent: Thursday, April 23, 2015 2:37 PM To: dev@cordova.apache.org Subject: Buildbot: buildslave cordova-ios-slave was lost The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named cordova-ios-slave went away It last disconnected at Thu Apr 23 21:31:41 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Your Name Here '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/cordova-ios-slave - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-android pull request: CB-8902: use immersive mode when ava...
GitHub user kicktheken opened a pull request: https://github.com/apache/cordova-android/pull/175 CB-8902: use immersive mode when available and "fullscreen" is set to 'true' "Fullscreen" preference set to 'true' in the config.xml should hide the navigation bar on android devices that support immersive mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kicktheken/cordova-android master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-android/pull/175.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #175 commit 1efc05d3e81523750c74753efcbaf26aaac6b6f0 Author: Kenneth Chan Date: 2015-04-23T21:40:37Z use immersive mode when available and "fullscreen" is set to 'true' --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Adding Other Platform Slaves to Medic
Hi Willy,
I ran your code on my own test machine, and it completes fine but it is still
missing the code to start a build:
http://cdv-ms-buildbot.cloudapp.net/builders/cordova-firefoxos-osx/builds/0/steps/running-tests/logs/stdio.
You will need to add code to make it actually build the app ("cordova build")
and run it (either "cordova run" or whatever commands are required to start
firefoxos). Before you add these changes, please also merge with the latest
changes in master (I tried, and it's clean: no conflicts).
Then, if firefoxos doesn't need anything special on a slave, your builds can
run on the existing slaves. If that is not the case, then you will need to
provide your own slave and connect it to Apache as described here:
https://github.com/MSOpenTech/cordova-medic/blob/master/SLAVES.md#connecting-to-apaches-master.
Kindly,
Dmitry
-Original Message-
From: Willy Aguirre [mailto:marti1...@gmail.com]
Sent: Wednesday, April 22, 2015 11:38 PM
To: dev@cordova.apache.org
Subject: Re: Adding Other Platform Slaves to Medic
any update? Dmitry
2015-04-20 1:10 GMT-05:00 Willy Aguirre :
> https://github.com/apache/cordova-medic/pull/39 my last commit is
> about createMedicJson
> a33637e960c930012905e> it works, yes can help with debug the slave.
>
> Regards,
>
> Willy
>
> 2015-04-17 22:09 GMT-05:00 Parashuram N (MS OPEN TECH) <
> panar...@microsoft.com>:
>
> In an earlier mail, folks had said that they would also contribute slaves.
>> Is there a process to begin that now ?
>>
>> On 4/17/15, 4:47 PM, "Dmitry Blotsky" wrote:
>>
>> >Hi list,
>> >
>> >Right now medic runs Android, iOS, Windows, and Windows Phone
>> >builds. The instructions for adding new slaves are here:
>> >
>> https://github.com/apache/cordova-medic/blob/master/SLAVES.md#connect
>> ing-t
>> >o-apaches-master
>> ><
>> https://github.com/apache/cordova-medic/blob/master/SLAVES.md#connect
>> ing-
>> >to-apaches-master>.
>> >
>> >Willy Aguirre has been working on adding FirefoxOS support. Willy,
>> >have you been able to successfully test your support locally with
>> >your changes? If so, you can follow the steps to add your slave to
>> >Apache. If you¹re running into issues, post them and we can debug.
>> >
>> >Kindly,
>> >Dmitry
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>
>
> --
> Willy Aguirre | @willrre
> Blog: http://osgux.tumblr.com/
> Mozilla Rep: https://reps.mozilla.org/u/Willy/ Mozilla Hispano -
> Willyaguirre
>
>
--
Willy Aguirre | @willrre
Blog: http://osgux.tumblr.com/
Mozilla Rep: https://reps.mozilla.org/u/Willy/ Mozilla Hispano - Willyaguirre
Re: [DISCUSS] Docs release
Hi Andrey. As we chatted on Hangout, I'll update the Russian docs but it'll take some time, please be patient. @Steven: I'll check those changes in other languages (as much as I can) 2015-04-23 13:19 GMT-05:00 Steven Gill : > I changed all references to org.apache.cordova.* to cordova-plugin-*. Docs > look good to publish I think. > > On Wed, Apr 22, 2015 at 8:31 PM, Andrey Kurdumov > wrote: > > > Could Viktor or Lisa update all untranslated Russian in CrowdIn. > > If I understand correclty, they could just use Microsoft translator for > > that and do that automatically. > > I have to do that manually, and I don't have cycles to fully > > translate/proofread language for this release. > > > > 2015-04-22 7:43 GMT+06:00 Sergey Grebnov (Akvelon) < > v-seg...@microsoft.com > > >: > > > > > I've sent a PR to update platform guides as per discussion in a > separate > > > thread; it will be great if we can review and include it to docs > release > > > > > > https://github.com/apache/cordova-docs/pull/279 > > > > > > Thx! > > > Sergey > > > -Original Message- > > > From: Steven Gill [mailto:stevengil...@gmail.com] > > > Sent: Tuesday, April 21, 2015 5:49 PM > > > To: dev@cordova.apache.org > > > Subject: [DISCUSS] Docs release > > > > > > I'm going to look into doing this. Any blockers, let me know > > > > > > Don't believe we have to vote on this one. > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > -- Victor Adrian Sosa Herrera IBM Software Engineer Guadalajara, Jalisco
Buildbot: buildslave cordova-ios-slave was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named cordova-ios-slave went away It last disconnected at Thu Apr 23 21:31:41 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Your Name Here '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/cordova-ios-slave - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request:
Github user jesman3 commented on the pull request: https://github.com/apache/cordova-lib/commit/281aee737dbe5143c9cb5957359ed5df6298a154#commitcomment-10876192 This breaks our plugin in our Windows 8.1 project. We just updated cordova internally and these changes were included in that. We have a plugin that has references added via the tag. These references are winmd files and require a dll to be in the same directory they reside in but this dll is not referenced in the jsproj. We were relying on the tag to put the dll in the location where it is needed like this now that this change has been implemented we get the error "not located within project!" from common.js. Although this might not be the actual intended use of the tag we have not been able to find another way to get this file into the correct target folder. Can this "ERROR" be changed to a "WARNING" instead. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Proposal: Expose check_reqs at the CLI level
Yes, check_reqs logic is still being executed on each build by platform build script and it's not executed in `platform add` --- Best regards, Vladimir -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Thursday, April 23, 2015 9:04 PM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Also, Vlad, can you confirm if check_reqs runs on build, or on platform add ? -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Thursday, April 23, 2015 11:00 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level My bad - I did not mean that this will run "when" platform is added. I mean, this can run only when a project is present and platform has already been added. For this first phase, we are not implementing this command for a platform that has not already been added to the project. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Thursday, April 23, 2015 10:52 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level You mean run but not error? Because, again, this code *used* to run when platforms were added -- except, that then it errored when the requirements weren’t satisfied. > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Thursday, April 23, 2015 1:23 PM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > I think as the first step, it would make sense to run it when platform > is added and project is present. We could change it later to run a system > wide check. > For now, this just picks up what check_reqs already does. > > We may need another effort to improve check_reqs itself. > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Thursday, April 23, 2015 1:28 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, Leo. Thanks for feedback! > > I've changed verb name to "requirements" because it looks like it is a > happy medium for the majority. > Updated code for cordova lib and cordova-cli submitted through the > following PRs: https://github.com/apache/cordova-cli/pull/212 > https://github.com/apache/cordova-lib/pull/208. > > Regarding your questions: > 1. The specification for command is exactly the same as you mentioned: > > cordova requirements [platform...] > > I've also added a help file to cordova-cli, so 'cordova help > requirements' will work now, and will provide all information about usage. > > 2. There are no special options for requirements command. There are > common options for all cli commands like '--sillent' and '--verbose' > and they're supported automatically. > > 3. The command requires a project and platform added to project. This > was the fastest way to implement it, and it could be changed in future > if we decide to support case when project doesn't exists. > > --- > Best regards, Vladimir > > -Original Message- > From: Treggiari, Leo [mailto:leo.treggi...@intel.com] > Sent: Wednesday, 22 April, 2015 18:11 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi Vladimir, > > It's great to see this being worked on and discussed. My comments > below are mine and mine alone. > > In addition to the code changes, I would have preferred to see a > specification of the command, e.g. > > cordova check-reqs platform [platform...] > > I took a quick look at the CLI code changes and didn't see any option > processing. Are there any options? > Do the platform(s) specified on the command need to have been already > added to the project? > Does the command require a project - i.e. be executed in a project directory? > Regarding the command name, I don't think being 'cute' is helpful to > users - i.e. I recommend against 'doctor'. > I think 'check-requirements' would be OK. It's long but how many > times does a user need to type it? > > Thanks, > Leo > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Wednesday, April 22, 2015 7:18 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, guys. Have anyone looked at it? > I've made some refactoring to make changes more readable, and updated > data contract between platform's check_reqs code and LIB API. > > Josh, regarding command name. I thought that there is still no > agreement about verb name. > Personally I agree that `cordova doctor` or `cordova requirements` > sounds better, but this is just a command name ant it could be changed at any > time. > > --- > Best regards, Vladimir > > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
Re: [DISCUSS] Docs release
I changed all references to org.apache.cordova.* to cordova-plugin-*. Docs look good to publish I think. On Wed, Apr 22, 2015 at 8:31 PM, Andrey Kurdumov wrote: > Could Viktor or Lisa update all untranslated Russian in CrowdIn. > If I understand correclty, they could just use Microsoft translator for > that and do that automatically. > I have to do that manually, and I don't have cycles to fully > translate/proofread language for this release. > > 2015-04-22 7:43 GMT+06:00 Sergey Grebnov (Akvelon) >: > > > I've sent a PR to update platform guides as per discussion in a separate > > thread; it will be great if we can review and include it to docs release > > > > https://github.com/apache/cordova-docs/pull/279 > > > > Thx! > > Sergey > > -Original Message- > > From: Steven Gill [mailto:stevengil...@gmail.com] > > Sent: Tuesday, April 21, 2015 5:49 PM > > To: dev@cordova.apache.org > > Subject: [DISCUSS] Docs release > > > > I'm going to look into doing this. Any blockers, let me know > > > > Don't believe we have to vote on this one. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
RE: Proposal: Expose check_reqs at the CLI level
Also, Vlad, can you confirm if check_reqs runs on build, or on platform add ? -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Thursday, April 23, 2015 11:00 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level My bad - I did not mean that this will run "when" platform is added. I mean, this can run only when a project is present and platform has already been added. For this first phase, we are not implementing this command for a platform that has not already been added to the project. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Thursday, April 23, 2015 10:52 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level You mean run but not error? Because, again, this code *used* to run when platforms were added -- except, that then it errored when the requirements weren’t satisfied. > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Thursday, April 23, 2015 1:23 PM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > I think as the first step, it would make sense to run it when platform > is added and project is present. We could change it later to run a system > wide check. > For now, this just picks up what check_reqs already does. > > We may need another effort to improve check_reqs itself. > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Thursday, April 23, 2015 1:28 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, Leo. Thanks for feedback! > > I've changed verb name to "requirements" because it looks like it is a > happy medium for the majority. > Updated code for cordova lib and cordova-cli submitted through the > following PRs: https://github.com/apache/cordova-cli/pull/212 > https://github.com/apache/cordova-lib/pull/208. > > Regarding your questions: > 1. The specification for command is exactly the same as you mentioned: > > cordova requirements [platform...] > > I've also added a help file to cordova-cli, so 'cordova help > requirements' will work now, and will provide all information about usage. > > 2. There are no special options for requirements command. There are > common options for all cli commands like '--sillent' and '--verbose' > and they're supported automatically. > > 3. The command requires a project and platform added to project. This > was the fastest way to implement it, and it could be changed in future > if we decide to support case when project doesn't exists. > > --- > Best regards, Vladimir > > -Original Message- > From: Treggiari, Leo [mailto:leo.treggi...@intel.com] > Sent: Wednesday, 22 April, 2015 18:11 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi Vladimir, > > It's great to see this being worked on and discussed. My comments > below are mine and mine alone. > > In addition to the code changes, I would have preferred to see a > specification of the command, e.g. > > cordova check-reqs platform [platform...] > > I took a quick look at the CLI code changes and didn't see any option > processing. Are there any options? > Do the platform(s) specified on the command need to have been already > added to the project? > Does the command require a project - i.e. be executed in a project directory? > Regarding the command name, I don't think being 'cute' is helpful to > users - i.e. I recommend against 'doctor'. > I think 'check-requirements' would be OK. It's long but how many > times does a user need to type it? > > Thanks, > Leo > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Wednesday, April 22, 2015 7:18 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, guys. Have anyone looked at it? > I've made some refactoring to make changes more readable, and updated > data contract between platform's check_reqs code and LIB API. > > Josh, regarding command name. I thought that there is still no > agreement about verb name. > Personally I agree that `cordova doctor` or `cordova requirements` > sounds better, but this is just a command name ant it could be changed at any > time. > > --- > Best regards, Vladimir > > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Monday, 20 April, 2015 22:04 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > This was only an initial implementation - no pull request has been > sent. I think this is just a way for folks to play with what Vlad has > now. I am sure we will change the verb name before a PR comes in. > > -Original Message- > From: Josh
RE: Proposal: Expose check_reqs at the CLI level
My bad - I did not mean that this will run "when" platform is added. I mean, this can run only when a project is present and platform has already been added. For this first phase, we are not implementing this command for a platform that has not already been added to the project. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Thursday, April 23, 2015 10:52 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level You mean run but not error? Because, again, this code *used* to run when platforms were added -- except, that then it errored when the requirements weren’t satisfied. > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Thursday, April 23, 2015 1:23 PM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > I think as the first step, it would make sense to run it when platform is > added > and project is present. We could change it later to run a system wide check. > For now, this just picks up what check_reqs already does. > > We may need another effort to improve check_reqs itself. > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Thursday, April 23, 2015 1:28 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, Leo. Thanks for feedback! > > I've changed verb name to "requirements" because it looks like it is a happy > medium for the majority. > Updated code for cordova lib and cordova-cli submitted through the > following PRs: https://github.com/apache/cordova-cli/pull/212 > https://github.com/apache/cordova-lib/pull/208. > > Regarding your questions: > 1. The specification for command is exactly the same as you mentioned: > > cordova requirements [platform...] > > I've also added a help file to cordova-cli, so 'cordova help requirements' > will > work now, and will provide all information about usage. > > 2. There are no special options for requirements command. There are > common options for all cli commands like '--sillent' and '--verbose' and > they're supported automatically. > > 3. The command requires a project and platform added to project. This was > the fastest way to implement it, and it could be changed in future if we > decide to support case when project doesn't exists. > > --- > Best regards, Vladimir > > -Original Message- > From: Treggiari, Leo [mailto:leo.treggi...@intel.com] > Sent: Wednesday, 22 April, 2015 18:11 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi Vladimir, > > It's great to see this being worked on and discussed. My comments below > are mine and mine alone. > > In addition to the code changes, I would have preferred to see a specification > of the command, e.g. > > cordova check-reqs platform [platform...] > > I took a quick look at the CLI code changes and didn't see any option > processing. Are there any options? > Do the platform(s) specified on the command need to have been already > added to the project? > Does the command require a project - i.e. be executed in a project directory? > Regarding the command name, I don't think being 'cute' is helpful to users - > i.e. I recommend against 'doctor'. > I think 'check-requirements' would be OK. It's long but how many times does > a user need to type it? > > Thanks, > Leo > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Wednesday, April 22, 2015 7:18 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, guys. Have anyone looked at it? > I've made some refactoring to make changes more readable, and updated > data contract between platform's check_reqs code and LIB API. > > Josh, regarding command name. I thought that there is still no agreement > about verb name. > Personally I agree that `cordova doctor` or `cordova requirements` sounds > better, but this is just a command name ant it could be changed at any time. > > --- > Best regards, Vladimir > > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Monday, 20 April, 2015 22:04 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > This was only an initial implementation - no pull request has been sent. I > think this is just a way for folks to play with what Vlad has now. I am sure > we > will change the verb name before a PR comes in. > > -Original Message- > From: Josh Soref [mailto:jso...@blackberry.com] > Sent: Monday, April 20, 2015 11:59 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > -1 > > Didn't everyone agree to call it `cordova doctor` or worst, `cordova > requirements`? > > > -Original Message- > > From: Vladi
RE: Proposal: Expose check_reqs at the CLI level
You mean run but not error? Because, again, this code *used* to run when platforms were added -- except, that then it errored when the requirements weren’t satisfied. > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Thursday, April 23, 2015 1:23 PM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > I think as the first step, it would make sense to run it when platform is > added > and project is present. We could change it later to run a system wide check. > For now, this just picks up what check_reqs already does. > > We may need another effort to improve check_reqs itself. > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Thursday, April 23, 2015 1:28 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, Leo. Thanks for feedback! > > I've changed verb name to "requirements" because it looks like it is a happy > medium for the majority. > Updated code for cordova lib and cordova-cli submitted through the > following PRs: https://github.com/apache/cordova-cli/pull/212 > https://github.com/apache/cordova-lib/pull/208. > > Regarding your questions: > 1. The specification for command is exactly the same as you mentioned: > > cordova requirements [platform...] > > I've also added a help file to cordova-cli, so 'cordova help requirements' > will > work now, and will provide all information about usage. > > 2. There are no special options for requirements command. There are > common options for all cli commands like '--sillent' and '--verbose' and > they're supported automatically. > > 3. The command requires a project and platform added to project. This was > the fastest way to implement it, and it could be changed in future if we > decide to support case when project doesn't exists. > > --- > Best regards, Vladimir > > -Original Message- > From: Treggiari, Leo [mailto:leo.treggi...@intel.com] > Sent: Wednesday, 22 April, 2015 18:11 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi Vladimir, > > It's great to see this being worked on and discussed. My comments below > are mine and mine alone. > > In addition to the code changes, I would have preferred to see a specification > of the command, e.g. > > cordova check-reqs platform [platform...] > > I took a quick look at the CLI code changes and didn't see any option > processing. Are there any options? > Do the platform(s) specified on the command need to have been already > added to the project? > Does the command require a project - i.e. be executed in a project directory? > Regarding the command name, I don't think being 'cute' is helpful to users - > i.e. I recommend against 'doctor'. > I think 'check-requirements' would be OK. It's long but how many times does > a user need to type it? > > Thanks, > Leo > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Wednesday, April 22, 2015 7:18 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hey, guys. Have anyone looked at it? > I've made some refactoring to make changes more readable, and updated > data contract between platform's check_reqs code and LIB API. > > Josh, regarding command name. I thought that there is still no agreement > about verb name. > Personally I agree that `cordova doctor` or `cordova requirements` sounds > better, but this is just a command name ant it could be changed at any time. > > --- > Best regards, Vladimir > > -Original Message- > From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] > Sent: Monday, 20 April, 2015 22:04 > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > This was only an initial implementation - no pull request has been sent. I > think this is just a way for folks to play with what Vlad has now. I am sure > we > will change the verb name before a PR comes in. > > -Original Message- > From: Josh Soref [mailto:jso...@blackberry.com] > Sent: Monday, April 20, 2015 11:59 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > -1 > > Didn't everyone agree to call it `cordova doctor` or worst, `cordova > requirements`? > > > -Original Message- > > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > > Sent: Monday, April 20, 2015 11:46 AM > > To: dev@cordova.apache.org > > Subject: RE: Proposal: Expose check_reqs at the CLI level > > > > Hi, list. > > > > I would like to share a draft implementation for check_reqs command > > and check_reqs API: > > Changes could be found here: > > CLI: https://github.com/apache/cordova- > > cli/compare/master...MSOpenTech:requirements_check > > LIB: https://github.com/apache/cordo
RE: Docs publishing and versioning
Please ignore this - I'm just catching up on my e-mail and saw the discuss thread for the docs release. It would be a good to get an idea of the versioning aspect though. Thanks, Nikhil -Original Message- From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] Sent: Thursday, April 23, 2015 9:47 AM To: dev@cordova.apache.org Subject: Docs publishing and versioning I'm not familiar with how docs get published to our website. I see the last version that was published was 4.0.0. By default, search results lead to this version and they are quite outdated. Should we publish a 5.0.0 version now that the tools release is out? Also, does the doc version match the cordova-lib release version? Did we miss 4.1 & 4.2 & 4.3? Thanks, Nikhil - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Proposal: Expose check_reqs at the CLI level
I think as the first step, it would make sense to run it when platform is added and project is present. We could change it later to run a system wide check. For now, this just picks up what check_reqs already does. We may need another effort to improve check_reqs itself. -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Thursday, April 23, 2015 1:28 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Hey, Leo. Thanks for feedback! I've changed verb name to "requirements" because it looks like it is a happy medium for the majority. Updated code for cordova lib and cordova-cli submitted through the following PRs: https://github.com/apache/cordova-cli/pull/212 https://github.com/apache/cordova-lib/pull/208. Regarding your questions: 1. The specification for command is exactly the same as you mentioned: cordova requirements [platform...] I've also added a help file to cordova-cli, so 'cordova help requirements' will work now, and will provide all information about usage. 2. There are no special options for requirements command. There are common options for all cli commands like '--sillent' and '--verbose' and they're supported automatically. 3. The command requires a project and platform added to project. This was the fastest way to implement it, and it could be changed in future if we decide to support case when project doesn't exists. --- Best regards, Vladimir -Original Message- From: Treggiari, Leo [mailto:leo.treggi...@intel.com] Sent: Wednesday, 22 April, 2015 18:11 To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Hi Vladimir, It's great to see this being worked on and discussed. My comments below are mine and mine alone. In addition to the code changes, I would have preferred to see a specification of the command, e.g. cordova check-reqs platform [platform...] I took a quick look at the CLI code changes and didn't see any option processing. Are there any options? Do the platform(s) specified on the command need to have been already added to the project? Does the command require a project - i.e. be executed in a project directory? Regarding the command name, I don't think being 'cute' is helpful to users - i.e. I recommend against 'doctor'. I think 'check-requirements' would be OK. It's long but how many times does a user need to type it? Thanks, Leo -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Wednesday, April 22, 2015 7:18 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Hey, guys. Have anyone looked at it? I've made some refactoring to make changes more readable, and updated data contract between platform's check_reqs code and LIB API. Josh, regarding command name. I thought that there is still no agreement about verb name. Personally I agree that `cordova doctor` or `cordova requirements` sounds better, but this is just a command name ant it could be changed at any time. --- Best regards, Vladimir -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Monday, 20 April, 2015 22:04 To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level This was only an initial implementation - no pull request has been sent. I think this is just a way for folks to play with what Vlad has now. I am sure we will change the verb name before a PR comes in. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Monday, April 20, 2015 11:59 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level -1 Didn't everyone agree to call it `cordova doctor` or worst, `cordova requirements`? > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Monday, April 20, 2015 11:46 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi, list. > > I would like to share a draft implementation for check_reqs command > and check_reqs API: > Changes could be found here: > CLI: https://github.com/apache/cordova- > cli/compare/master...MSOpenTech:requirements_check > LIB: https://github.com/apache/cordova- > lib/compare/master...MSOpenTech:requirements_check > Cordova-android: https://github.com/apache/cordova- > android/compare/master...MSOpenTech:requirements_check > > The implementation consists of following: > 1. 'cordova check-reqs' command for cordova CLI, which calls > corresponding cordova-lib API with options, specified from CLI > > 2. 'check_reqs' module for cordova-lib, which works as a wrapper > around platforms' check_reqs scripts. It returns a promise, either > resolved if check_reqs platform script is found and ran successfully > or rejected in case if check_reqs script is failed du
Docs publishing and versioning
I'm not familiar with how docs get published to our website. I see the last version that was published was 4.0.0. By default, search results lead to this version and they are quite outdated. Should we publish a 5.0.0 version now that the tools release is out? Also, does the doc version match the cordova-lib release version? Did we miss 4.1 & 4.2 & 4.3? Thanks, Nikhil
[GitHub] cordova-blackberry pull request: CB-8899 stick to grunt-jasmine-no...
GitHub user dylin opened a pull request: https://github.com/apache/cordova-blackberry/pull/183 CB-8899 stick to grunt-jasmine-node@0.2.1 It has issue to run `grunt test` with the new version of grunt-jasmine-node when set matchall true, but it works with 0.2.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/blackberry/cordova-blackberry danylin/CB-8899 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-blackberry/pull/183.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #183 commit 617e176c8ef9a9f0f4e638a7fd6dc23699644ff6 Author: Danyi Lin Date: 2015-04-23T15:46:38Z CB-8899 stick to grunt-jasmine-node@0.2.1, the new version has issue when set matchall true --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-device-motion pull request: CB-8876 Rewrote wp8 imp...
Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-device-motion/pull/27 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-media pull request: CB-8888 Makes media status repo...
Github user alsorokin commented on the pull request: https://github.com/apache/cordova-plugin-media/pull/52#issuecomment-95577632 Tested on my box and emulator, it works for me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-camera pull request: solves CB-8804 https://github....
Github user thehuijb commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-camera/pull/83#discussion_r28956355
--- Diff: src/android/CameraLauncher.java ---
@@ -163,7 +167,15 @@ else if ((srcType == PHOTOLIBRARY) || (srcType ==
SAVEDPHOTOALBUM)) {
PluginResult r = new
PluginResult(PluginResult.Status.NO_RESULT);
r.setKeepCallback(true);
callbackContext.sendPluginResult(r);
-
+
+return true;
+} else if (action.equals("checkForSavedResult")) {
+this.imageUri = Uri.fromFile(createCaptureFile(JPEG));
--- End diff --
right , should also do this when savedResultCode > 0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-plugin-device-motion pull request: CB-8876 Rewrote wp8 imp...
GitHub user alsorokin opened a pull request: https://github.com/apache/cordova-plugin-device-motion/pull/27 CB-8876 Rewrote wp8 impementation to be more stable https://issues.apache.org/jira/browse/CB-8876 You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-plugin-device-motion CB-8876 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-device-motion/pull/27.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #27 commit 3950ab7b6b3f8fb74896ec3ee0d77e52773a38c6 Author: alsorokin Date: 2015-04-23T08:32:31Z CB-8876 Rewrote wp8 impementation to be more stable --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Deprecation Wars: ICS vs Gingerbread
What about minimum updating the blog post? On Wednesday, April 22, 2015, Andrew Grieve wrote: > Not sure it's worth doing another release just for this. Devs can already > set the minSdkVersion using a . > > On Wed, Apr 22, 2015 at 5:33 PM, Joe Bowser > wrote: > > > BTW: Sorry for rushing the commit and sticking the ugly merge commit to > try > > and fix it. > > > > On Wed, Apr 22, 2015 at 2:28 PM Steven Gill > > > wrote: > > > > > Okay. Since pluggable webviews don't work with 2.3.x, I'd say we do a > > > cordova-android 4.1.0 release with minsdk 14. > > > > > > I'll update the docs to say we only support android 4+ > > > > > > On Wed, Apr 22, 2015 at 2:24 PM, Joe Bowser > wrote: > > > > > > > As in they don't work on Android 2.3.x, sorry hit send way too soon. > > > Also, > > > > there's a lot of bad security issues on 2.3.x that we just can't fix, > > so > > > > it's best that we draw the line here and not support 2.3.x > > > > > > > > On Wed, Apr 22, 2015 at 2:23 PM Joe Bowser > wrote: > > > > > > > > > None of the Third Party WebViews work for 4.0.x > > > > > > > > > > On Wed, Apr 22, 2015 at 2:19 PM Steven Gill < > stevengil...@gmail.com > > > > > > wrote: > > > > > > > > > >> 4.1.0? Is the minsdk the only thing keeping gingerbread support > > > around? > > > > >> Are > > > > >> there other things about 4.0.0 that broke support for 2.3.0? > > > > >> > > > > >> > > > > >> > > > > >> On Wed, Apr 22, 2015 at 2:13 PM, Joe Bowser > > > > wrote: > > > > >> > > > > >> > OK, because we screwed up, should we release a Cordova-Android > > 5.0? > > > > >> This > > > > >> > is going to break people, even though I don't care about the > > > breakage, > > > > >> I do > > > > >> > care about telling them about the breakage. > > > > >> > > > > > >> > Thoughts? > > > > >> > > > > > >> > On Wed, Apr 22, 2015 at 2:10 PM Joe Bowser > > > > wrote: > > > > >> > > > > > >> > > It should be replaced with 14. This was definitely an > oversight > > > > >> since we > > > > >> > > all agreed in theory but never came to a proper decision. > > > > >> > > > > > > >> > > On Wed, Apr 22, 2015 at 12:20 PM Sergey Grebnov (Akvelon) < > > > > >> > > v-seg...@microsoft.com > wrote: > > > > >> > > > > > > >> > >> I still see minSdkVersion = 10 (GINGERBREAD) in platform > > > template. > > > > >> > Should > > > > >> > >> it be replaced w/ 14 (ICE_CREAM_SANDWICH) in this case and > also > > > > >> updated > > > > >> > in > > > > >> > >> platform docs? - per docs we still support Gingerbread. > > > > >> > >> > > > > >> > >> Steve is currently working on docs update so this is perfect > > time > > > > to > > > > >> > >> change this. > > > > >> > >> > > > > >> > >> -Sergey > > > > >> > >> -Original Message- > > > > >> > >> From: Shazron [mailto:shaz...@gmail.com ] > > > > >> > >> Sent: Tuesday, April 21, 2015 1:04 PM > > > > >> > >> To: dev@cordova.apache.org > > > > >> > >> Subject: Re: Deprecation Wars: ICS vs Gingerbread > > > > >> > >> > > > > >> > >> Joe, perhaps that can be part of the Tools Release blog post? > > > Steve > > > > >> put > > > > >> > >> out a link to the draft in another thread. > > > > >> > >> > > > > >> > >> On Tue, Apr 21, 2015 at 10:14 AM, Joe Bowser < > > bows...@gmail.com > > > > > >> wrote: > > > > >> > >> > Resurrecting this thread! > > > > >> > >> > > > > > >> > >> > I think we need to let our users know that Cordova 4.0 > > doesn't > > > > >> support > > > > >> > >> > Gingerbread, or at least some of the features don't work on > > > > >> > Gingerbread. > > > > >> > >> > I've been trying to clean up the JIRA a bit today, and it > > seems > > > > >> that > > > > >> > >> > while we came to a consensus to drop 2.3, we didn't tell > > > anyone. > > > > :/ > > > > >> > >> > > > > > >> > >> > > > > > >> > >> > On Tue, Jan 13, 2015 at 12:41 PM Joe Bowser < > > bows...@gmail.com > > > > > > > > >> > wrote: > > > > >> > >> > > > > > >> > >> >> Firefox works on 2.3, and Chrome does not. It also depends > > on > > > > the > > > > >> > >> >> device > > > > >> > >> >> > > > > >> > >> >> On Tue, Jan 13, 2015, 12:20 PM Josh Soref < > > > > jso...@blackberry.com > > > > > >> > >> wrote: > > > > >> > >> >> > > > > >> > >> >>> Michal Mocny wrote: > > > > >> > >> >>> >... we aren't telling those individuals that they cannot > > use > > > > >> their > > > > >> > >> >>> >phones, we are telling developers that want to create > new > > > > >> > >> >>> >applications for that target to either build mobile web, > > > > >> packaged > > > > >> > >> >>> >native, or just stick to existing versions of cordova if > > > > really > > > > >> > >> needed. > > > > >> > >> >>> > > > > > >> > >> >>> >I do not buy the argument that you are doing those > > > individuals > > > > >> with > > > > >> > >> >>> >those phones a favour by building them hybrid apps using > > the > > > > >> > >> >>> >antiquated 2.3 webview on antiquated machine specs. > > > > >> > >> >>> > > > > >> > >> >>> I don't have an opinion on this. But I do have a > q
RE: Proposal: Expose check_reqs at the CLI level
Hey, Leo. Thanks for feedback! I've changed verb name to "requirements" because it looks like it is a happy medium for the majority. Updated code for cordova lib and cordova-cli submitted through the following PRs: https://github.com/apache/cordova-cli/pull/212 https://github.com/apache/cordova-lib/pull/208. Regarding your questions: 1. The specification for command is exactly the same as you mentioned: cordova requirements [platform...] I've also added a help file to cordova-cli, so 'cordova help requirements' will work now, and will provide all information about usage. 2. There are no special options for requirements command. There are common options for all cli commands like '--sillent' and '--verbose' and they're supported automatically. 3. The command requires a project and platform added to project. This was the fastest way to implement it, and it could be changed in future if we decide to support case when project doesn't exists. --- Best regards, Vladimir -Original Message- From: Treggiari, Leo [mailto:leo.treggi...@intel.com] Sent: Wednesday, 22 April, 2015 18:11 To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Hi Vladimir, It's great to see this being worked on and discussed. My comments below are mine and mine alone. In addition to the code changes, I would have preferred to see a specification of the command, e.g. cordova check-reqs platform [platform...] I took a quick look at the CLI code changes and didn't see any option processing. Are there any options? Do the platform(s) specified on the command need to have been already added to the project? Does the command require a project - i.e. be executed in a project directory? Regarding the command name, I don't think being 'cute' is helpful to users - i.e. I recommend against 'doctor'. I think 'check-requirements' would be OK. It's long but how many times does a user need to type it? Thanks, Leo -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Wednesday, April 22, 2015 7:18 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Hey, guys. Have anyone looked at it? I've made some refactoring to make changes more readable, and updated data contract between platform's check_reqs code and LIB API. Josh, regarding command name. I thought that there is still no agreement about verb name. Personally I agree that `cordova doctor` or `cordova requirements` sounds better, but this is just a command name ant it could be changed at any time. --- Best regards, Vladimir -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Monday, 20 April, 2015 22:04 To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level This was only an initial implementation - no pull request has been sent. I think this is just a way for folks to play with what Vlad has now. I am sure we will change the verb name before a PR comes in. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Monday, April 20, 2015 11:59 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level -1 Didn't everyone agree to call it `cordova doctor` or worst, `cordova requirements`? > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Monday, April 20, 2015 11:46 AM > To: dev@cordova.apache.org > Subject: RE: Proposal: Expose check_reqs at the CLI level > > Hi, list. > > I would like to share a draft implementation for check_reqs command > and check_reqs API: > Changes could be found here: > CLI: https://github.com/apache/cordova- > cli/compare/master...MSOpenTech:requirements_check > LIB: https://github.com/apache/cordova- > lib/compare/master...MSOpenTech:requirements_check > Cordova-android: https://github.com/apache/cordova- > android/compare/master...MSOpenTech:requirements_check > > The implementation consists of following: > 1. 'cordova check-reqs' command for cordova CLI, which calls > corresponding cordova-lib API with options, specified from CLI > > 2. 'check_reqs' module for cordova-lib, which works as a wrapper > around platforms' check_reqs scripts. It returns a promise, either > resolved if check_reqs platform script is found and ran successfully > or rejected in case if check_reqs script is failed due to some internal > errors or not found at all. > > 3. check_reqs script for android platform, updated to return array of > requirements. > > * Each requirements is an object with following fields: > - id - some short id, could be useful for tools, that consume API > directly > - name - readable name for this requirement, such as 'Jav JDK' > or 'Gradle build tools', etc. > - installed - Boolean paremeter that indicates if requirement > is properly install
[GitHub] cordova-cli pull request: CB-8898 Introduces `cordova requirements...
GitHub user vladimir-kotikov opened a pull request: https://github.com/apache/cordova-cli/pull/212 CB-8898 Introduces `cordova requirements` command This is implementation for [CB-8898](https://issues.apache.org/jira/browse/CB-8898) which adds `cordova requirements` command. This PR requires https://github.com/apache/cordova-lib/pull/208 to be merged as well You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-cli CB-8898 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/212.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #212 commit 04d4e5067bb41486b813ac0d6269b7e500b58a9b Author: Vladimir Kotikov Date: 2015-04-23T07:55:30Z CB-8898 Introduces `cordova requirements` command --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] cordova-lib pull request: CB-8898 Introduces `requirements` cordov...
GitHub user vladimir-kotikov opened a pull request: https://github.com/apache/cordova-lib/pull/208 CB-8898 Introduces `requirements` cordova module This is implementation for [CB-8898](https://issues.apache.org/jira/browse/CB-8898) which adds `requirements` module, used by CLI. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-lib CB-8898 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/208.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #208 commit d24bd9690d0a5a69c00d06e62bb475bc2a405ac1 Author: Vladimir Kotikov Date: 2015-04-23T07:56:53Z CB-8898 Introduces `requirements` cordova module --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
