RE: Google Analytics on Cordova Docs
+1 to adding analytics to docs too. I think this will also help us concentrate on specific types of docs. We will know if people like tutorial like things or references. -Original Message- From: Andrey Kurdumov [mailto:kant2...@googlemail.com] Sent: Tuesday, June 23, 2015 12:18 AM To: dev@cordova.apache.org Subject: Google Analytics on Cordova Docs Hi all, I see the usage of Google Analytics on the main Crodova website. Would be good to have docs pages tracking too. For me personally very interesting which translation pages is most visited and thus which of them I have to proofread first. Another interested metric is which version of docs are more visited. I have experience that peoples without knowing look at the wrong version of docs. What do you think about such initiative? - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Cordova-Windows Release
+1 to merging Cordova-windows10 in master. I don't think it breaks anything existing, and windows10 support seems to be enabled only via flags or cli args. I think merging it into master will make developing windows 10 easier. -Original Message- From: Rob Paveza [mailto:rob.pav...@microsoft.com] Sent: Tuesday, May 12, 2015 11:39 AM To: dev@cordova.apache.org Subject: [DISCUSS] Cordova-Windows Release Does anyone have a reason to delay a cordova-windows platform release? Any outstanding patches to land? I'm looking to merge Windows 10 support into main and release 4.0.0. If not, I will start a release tomorrow. Thanks, -Rob - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Rapid release of tools
I think we should do an accelerated vote - 72 hour window is only a suggestion, and if the community believes, we should start a DISCUSS and a VOTE thread soon. -Original Message- From: Chuck Lantz [mailto:cla...@microsoft.com] Sent: Thursday, May 7, 2015 12:13 PM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Rapid release of tools Definitely. Note that 4.3.0 is also broken - We likely need to look at a 4.3.1 given the level of change in 5.0.0. -Chuck -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Thursday, May 7, 2015 12:08 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Rapid release of tools I am thinking we release off our previous release branches with this one change. This needs to get out asap. I'm all for an accelerated vote. On Thu, May 7, 2015 at 12:05 PM, Jesse purplecabb...@gmail.com wrote: Given that all downstream distributions are broken currently, can we do an accelerated vote? Are we introducing any other code that would slow us down? or can we simply update+republish package.json files? @purplecabbage risingj.com On Thu, May 7, 2015 at 12:01 PM, Steven Gill stevengil...@gmail.com wrote: I think we should do a quick release to get npm install cordova working again asap. I have updated the browserify dependency on cordova-js which fixes the problem. Need to release cordova-js@3.9.1, cordova-lib@5.0.1, cordova-cli@5.0.1 and plugman@0.23.2 with the new dependency. - 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: Windows Phone Screen resolution
Are you building this for Windows 8 or Windows 8.1 ? These are specified in the appmanifest. -Original Message- From: Ross Gardler (MS OPEN TECH) [mailto:ross.gard...@microsoft.com] Sent: Monday, May 4, 2015 6:01 PM To: dev@cordova.apache.org Subject: Windows Phone Screen resolution I'm trying to submit my first Cordova app to the Windows Phone store. One of the problems I'm getting is that the resulting application requires a limited set of resolutions (WVGA, 720P, WXGA). According to the Windows Store Dashboard this information is pulled from the package details I uploaded. I don't see anything in my config about resolutions. How are these resolutions determined? Ross - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [Discuss] Plugins release
These changes will only impact Windows platform, and windows10 for that matter, right ? If that is the case, I think we should do a quick release. -Original Message- From: Rob Paveza [mailto:rob.pav...@microsoft.com] Sent: Friday, May 1, 2015 10:25 AM To: dev@cordova.apache.org Subject: [Discuss] Plugins release I'd like to start a plugins release soon. With the release of the final version of Windows 10, I've seen some breaks in plugins in Windows 10. A big detractor has been that Windows 10 doesn't support AnyCPU for C# libraries or references anymore, and then the other common thing that has come up is that code tests for Phone, but Windows 10 always treats it as just one platform so the test is never true. Because there are incomplete changes in a few master branches, I'm thinking of cherry-picking and just bumping the small version parameter (e.g., 1.0.0 - 1.0.1). Here are the plugins that need updates: - cordova-plugin-device-motion - Jira: https://issues.apache.org/jira/browse/CB-8926 - Pull request / commit: https://github.com/apache/cordova-plugin-device-motion/pull/29 - cordova-plugin-dialogs - Jira: https://github.com/apache/cordova-plugin-device-motion/pull/29 - Pull request / commit: https://github.com/apache/cordova-plugin-dialogs/pull/52 - cordova-plugin-vibration - Jira: https://issues.apache.org/jira/browse/CB-8930 - Pull request / commit: https://github.com/apache/cordova-plugin-vibration/pull/34 - cordova-plugin-camera - Jira: https://issues.apache.org/jira/browse/CB-8943 - Commit: https://github.com/MSOpenTech/cordova-plugin-camera/commit/4c3ba18ae328efcdf6826bc22c84083ccc12af38 . We can't do a PR here because there are manual merges involved into master. We know that there needs to be one, we'll have one soon. Pulling in these changes will allow devs who want to try out Windows 10 to work. They also fix manual tests run in mobile-spec. Thanks, -Rob - 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: Best place to browse plugins
The mirroring may not help for search, but my worry is that a lot of folks would still be on 4.3.0 and when cordova plugins registry becomes read only, they would not get bug fixes and other plugin updates. -Original Message- From: Victor Sosa [mailto:sosah.vic...@gmail.com] Sent: Friday, May 1, 2015 8:59 AM To: dev@cordova.apache.org Subject: Re: Best place to browse plugins I don't see a value on mirroring either. Instead I'd like to see a good querying mechanism in NPM, but for that we have to wait :/ 2015-05-01 10:55 GMT-05:00 Raymond Camden raymondcam...@gmail.com: I don't know - if npm is the place, then having a mirror just seems like noise. I'd say close it down and put a nice text message up on the site explaining where it is at NPM and how to search. (Link to npm with the search params included.) Is there a benefit of having it mirrored? On Fri, May 1, 2015 at 10:49 AM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: It would be even better (for backward compatibility reasons) if we could simply publish on npm, but keep plugins.cordova.io as a mirror/redirector, based on the Cordova registry mapper. -Original Message- From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] Sent: Friday, May 1, 2015 8:31 AM To: dev@cordova.apache.org Subject: Re: Best place to browse plugins What is the plan for plugins.cordova.io for after the CPR is closed? Without knowing if there is a good way to retrieve the list/details of the cordova plugins from npm. I would love it if we could keep it as it is with the data from npm. -- Gorkem On 29 Apr 2015, at 10:57, Raymond Camden wrote: With plugins at npm now, what is the best place for users to browse plugins? Is it at npm, using the search filter? https://www.npmjs.com/browse/keyword/ecosystem:cordova Is it plugins.cordova.io? If it is npm, will there be text added to plugins.cordova.io to tell folks to start using the npm site? -- === === = Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden --- -- 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 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org -- == = Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - 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
RE: Best place to browse plugins
It would be even better (for backward compatibility reasons) if we could simply publish on npm, but keep plugins.cordova.io as a mirror/redirector, based on the Cordova registry mapper. -Original Message- From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] Sent: Friday, May 1, 2015 8:31 AM To: dev@cordova.apache.org Subject: Re: Best place to browse plugins What is the plan for plugins.cordova.io for after the CPR is closed? Without knowing if there is a good way to retrieve the list/details of the cordova plugins from npm. I would love it if we could keep it as it is with the data from npm. -- Gorkem On 29 Apr 2015, at 10:57, Raymond Camden wrote: With plugins at npm now, what is the best place for users to browse plugins? Is it at npm, using the search filter? https://www.npmjs.com/browse/keyword/ecosystem:cordova Is it plugins.cordova.io? If it is npm, will there be text added to plugins.cordova.io to tell folks to start using the npm site? -- == = Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - 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 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Does Cordova have a problem making developers happy?
I think we had some really great ideas here and I think as a community, we can
make Cordova better by improving our documentation.
I started a new Proposal here -
https://github.com/cordova/cordova-discuss/blob/master/proposals/ImprovedDocumentation.md
to try and collect topics for articles that may be helpful, and add
suggestions. It would be great if folks who responded on the thread add their
ideas to the document.
-Original Message-
From: Frederico Galvão [mailto:frederico.gal...@pontoget.com.br]
Sent: Wednesday, April 22, 2015 7:11 AM
To: dev
Subject: Re: Does Cordova have a problem making developers happy?
As someone who has given a couple of local speechs and presentations about
Cordova, I could say with some certainty that most of the time what makes
Cordova a not-so-well known tool is the misconception about what it's aimed at
doing, and incoherent expectations towards what it CAN do for the developer.
Other than that, and all the small things that have been already mentioned
previously by everyone, I'd say that web development (the one out there, not
the one defined by ES{6,7,8} or future dream
tools/standards/frameworks) in general is still not ready to what is needed for
mobile development to be taken seriously and be able to build complex
applications successfully. Very few development teams have enough awareness of
how much more is needed on a well built application other than jQuery and 256
plugins.
In the end, everything sums up to how well defined expectations are. And I'm
sure Cordova, along with its website and documentation, can be a lot better at
guiding developers to better expectations towards everything that can be
expected from cordova, and what can't.
I'm interested in contributing to this in whatever small way I can.
2015-04-19 21:48 GMT-03:00 Parashuram N (MS OPEN TECH)
panar...@microsoft.com:
I think FAQs, tutorials and blogs are great. I would also like to
contribute to this. Maybe a good start would be to identify a the
topics that require a blog post ?
If we have a list of things to blog about, I am sure the community can
come up with the actual articles and blog posts.
I am sure my team would love to help with the content. Should we start
putting together a list of topics that would need tutorials ?
-Original Message-
From: Kerri Shotts [mailto:kerrisho...@gmail.com]
Sent: Monday, April 13, 2015 8:57 PM
To: dev@cordova.apache.org
Subject: Re: Does Cordova have a problem making developers happy?
I had similar ideas about writing some FAQs or posts. Great minds
clearly think alike, right? ;-) (I’m joking. I know my mind… so not
great… Wait… that might actually be an insult to everyone else. The
only way to win is not to play! Aah! Clearly I need to go to
bed. I’ve been staring at my latest book’s chapter for way too long.)
In fact, I’ve toyed with the idea of doing some screencasts using
Cordova and the various tools I use with it (like gulp, browserify,
and babeljs), and these could make some excellent topics as well.
Especially debugging, because it’s not always enough just to say
“here’s where you go to start debugging remotely”. Debugging is a
skill (an art, really), so I could see a lot from that topic alone,
but geared more directly at typical debugging issues one finds in Cordova
dev. Hmm. Where to find the hours in the day?
Or a clone… I could really use a clone…
From: Raymond Camden raymondcam...@gmail.com
Reply: dev@cordova.apache.org dev@cordova.apache.org
Date: April 13, 2015 at 8:18:39 PM
To: dev@cordova.apache.org dev@cordova.apache.org
Subject: Re: Does Cordova have a problem making developers happy?
Like Tommy, I may steal some of these for blog posts -
People is having troubles connecting with the server, some of them
because use localhost as the url, others because they don't
configure the whitelist properly, others for unknow reasons
As for the debug one, I ask, Do you know how to remote debug? about
5-10 times a week now. Sadly, now that it is so DARN easy to debug,
folks just don't seem to know they CAN do it.
On Mon, Apr 13, 2015 at 6:49 PM, tommy-carlos williams
to...@devgeeks.org
wrote:
If no one else has time to do something with this list by the time I
get
free of my current stress-pile (say a couple weeks from now), I would
love to take a crack at it. An FAQ with not just the list, but actual
solutions and examples would be a great resource.
Even if someone else does it, I might use it as the basis for a
series of blog posts or something. It’s such a good summary of
people’s frustrations. I would probably even have one or two to add
from the #phonegap IRC channel.. :/
--
tommy-carlos williams
On 14 April 2015 at 08:16:56, Josh Soref (jso...@blackberry.com) wrote:
So, I want someone to make this into a FAQ, somehow.
I don't have time today, but it's a really great list.
Bonus
Re: Does cordova-mobile-spec support CLI build?
Just out of curiosity, what are you using mobile spec for ? Are you using this to test non-core plugins ? Would be interesting to see how mobile-spec fares on that. On 4/28/15, 9:35 PM, Rob Paveza rob.pav...@microsoft.com wrote: Try out this at your command line: cordova-coho/coho for-each git pull cordova-coho/coho for-each npm install cordova-coho/coho npm-link I had to go through that process today, so maybe it'll work for you too! From: Lin, Wanming wanming@intel.com Sent: Tuesday, April 28, 2015 6:47 PM To: dev@cordova.apache.org Subject: Does cordova-mobile-spec support CLI build? Hello I use cordova-mobile-spechttps://github.com/apache/cordova-mobile-spec for several months with great experience, but the test suite build. I follow the steps in README.mdhttps://github.com/apache/cordova-mobile-spec/blob/master/README .md, which is extremely complex and tedious. User have to pull many git repos, cordova-cli, cordova-plugman, cordova-js, cordova-android, cordova-coho... then pull npm packages, make npm link... Is there a simpler way? Can it be possible to build via Cordova CLI? Really appreciate all your help in advance. Thanks, Wanming - 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: Two small tools for Cordova
+1 to adding it to Coho, specially the first script - would be a good sanity check before releasing !! On 4/27/15, 7:27 AM, Andrew Grieve agri...@chromium.org wrote: Thanks Murat! Sounds really useful! WDYT about integrating these with coho? - So that cordova devs don't need to npm install multiple dev commands - So that the commands will be more discoverable - So that you can restrict to repos: e.g. coho travis -r plugins On Sun, Apr 26, 2015 at 11:53 PM, Murat Sutunc mura...@microsoft.com wrote: Hey everyone, I've been working on two side projects that I think others might also find useful. Cordova Travis (https://www.npmjs.com/package/cordova-travis) Prints out the latest travis build result on console; for all Apache Cordova repos. Whenever there's something red, it's time to fix something :) Cordova Stale (https://www.npmjs.com/package/cordova-stale) This is more to help with our personal repos. Once a PR is merged we often forget to delete our own local branch. This tool helps to identify stale branches. Hope these would be useful. Thanks! Murat - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Experimenting with API for cordova tooling
Should we move this docs to cordova-discuss instead -https://github.com/cordova/cordova-discuss ? On 4/24/15, 4:02 PM, Mark Koudritsky kam...@google.com wrote: I'm back from ApacheCon and vacation. Very glad to see some enthusiasm about this! My thoughts about the next steps turned out to be rather lengthy so here is a doc: https://docs.google.com/document/d/1jxQvygBtTeCYhxMtHLD9jgKTKZofMJdux1UIzs dd5b0 The most important next steps are: - Take one platform and try combine the logic from cordova/metadata and plugman/platforms for it. This will help figure out some details. - Improve plugin (un)install logic in PlatformProject so that the CLI can be eventually implemented in terms of PlatformProject. Comments and discussion will be greatly appreciated! On Wed, Apr 15, 2015 at 1:52 PM, Michal Mocny mmo...@chromium.org wrote: Great enthusiasm! Mark is currently at ApacheCon and then taking a few vacation days, so I'm not sure if he will answer this quickly. Figured I'd chime in for now. I think that exactly as you say, the PlatformProject work was started by Mark as a way to separate the divide between platforms and lib. This experiment I think came out of discussions on how best to move out the platform parsers (search ML for Move platform parsers from CLI to platforms started by Steven Gill). I also emphasize earlier points that these are experiments and are totally open for re-design. I don't have concrete steps to propose for going forward, but sounds like you already have some good ideas. Another topic that came out of discussion at Hangout was to create a cleaner cordova-lib-core, still leaving it within the cordova-lib repo. High-level strawman suggests this core would not do various input parsing or make any assumptions about project directory structure, but would have a very strict and simple interface, which various higher levels use to do with it what they will. -Michal On Wed, Apr 15, 2015 at 12:33 PM, Rob Paveza rob.pav...@microsoft.com wrote: This is a cool project. I'm curious, how much work do you think it'd be to refactor the cordova CLI to interact with the projects via the PlatformProject interface? We've been talking about how we could pull some of the cordova-lib platform-specific dependencies out and put them into the platforms (one example that comes to mind is having platform-specific parameters on plugin), so that platform-specific code lives in the platform implementation rather than cordova-lib. Having each platform derive from PlatformProject seems like an excellent first step, since (at least between -lib and -windows) once -lib hands off the project to the platform code, it's just go time. What do you think the next steps are in terms of your API shape and plans? Where do you see needing help most, where can I pitch in to get your project going more? -Original Message- From: Mark Koudritsky [mailto:kam...@google.com] Sent: Friday, April 10, 2015 12:50 PM To: dev@cordova.apache.org Subject: Experimenting with API for cordova tooling From today's hangout discussion, here are the links to our experiments with using cordova tooling via API rather than CLI. It is loosely based on my older experiments here https://github.com/kamrik/CordovaGulpTemplate But his time there is a separate wrapper that exposes a more object oriented API and reaches deeper into cordova-lib. It introduces a central object called PlatformProject that represents a single platform. The wrapper is here: https://github.com/kamrik/CordovaPlatformProject Please consider it experimental and feel free to fork and play with it. A demo app that uses this wrapper https://github.com/kamrik/cordova-api-example The ServiceWorker-to-Cordova script that uses the same wrapper https://github.com/MobileChromeApps/sw2cdv I'll also be giving a presentation about this at ApacheCon next week, draft slides are here http://kamrik.org/PlatformProjectSlides - 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
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: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Monday, April 20, 2015 11:46 AM To: dev@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 due to some internal errors
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 Soref [mailto:jso...@blackberry.com] Sent: Monday, April 20, 2015 11:59 AM To: dev@cordova.apache.org
RE: Scoped package names for npm?
Scopes are like namespaces. In the reverse domain name world, org.apache.cordova was considered a namespace, right ? We did not want non core packages to publish to that namespace, so does the same argument apply ? Alternatively, we can think of scope as packages that apply to a particular environment - for example, all cordova packages would be @cordova scope. -Original Message- From: Michal Mocny [mailto:mmo...@google.com] Sent: Monday, April 20, 2015 2:03 PM To: dev Subject: Re: Scoped package names for npm? Other questions to answer: - Can 3rd-parties publish to this scope? - Do we want them to? - Do we want to default to @cordova scope if none is provided, such that you could do `cordova plugin add device`? -Michal On Mon, Apr 20, 2015 at 5:00 PM, Michal Mocny mmo...@google.com wrote: https://docs.npmjs.com/getting-started/scoped-packages Should we be @cordova/plugin-device instead of cordova-plugin-device? -Michal
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 installed/satisfied - reason - error, reported by requirements check routines if requirement is missing. Please note that work is still in progress, and will be changed according to review comments. TBD: * move presentation logic from LIB to CLI; * refine data format, returned by cordova-lib API * add other platforms * and more... :) --- Best regards, Vladimir -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Monday, 20 April, 2015 3:49 To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level Looks like implementing a global level check_reqs without a project seems harder, I would suggest we make it a part of a second phase of this implementation. For now, we have a basic version that simply abstracts out existing check_reqs into a separate, platform level command. This could be a good first phase, and should also give us an idea about how developers use this command. As a part of Phase 2, anyone from the community should be able to build on a cordova level check reqs, and possibly extend it to checking reqs when no project is present. -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Wednesday, April 15, 2015 8:53 AM To: dev@cordova.apache.org Subject: RE: Proposal: Expose check_reqs at the CLI level We already support: `cordova build android` There's no need for the extra `platform` verb.. But, `cordova build android --nobuild` isn't any more intuitive than w/ the extra platform. And yes, as I noted, and others have noted, we used to run check_reqs in add, we're not going back to doing that. A `cordova doctor` or `cordova requirements` verb seems fine. I'm also fine `cordova doctor PLATFORM` instead of `cordova platform doctor PLATFORM`, As for when someone is likely to want to ask what requirements do I need for a platform, it's fairly arbitrary. Someone who is given a project might know that they don't have the environment for a platform, they aren't likely to want to go down a build rabbit hole, so, I'm -1 on hiding it anywhere near build. It's perfectly reasonable from my perspective for someone to want to run `cordova requirements PLATFORM` without a project at all. Imagine someone is getting started, they install cordova, and know they want to develop for PLATFORM, they could reasonably want to set up their requirements for that platform before trying to create a project... I don't know if anyone's check_reqs scripts actually requires a project, I actually think they don't, so it's probably sufficient to run them straight from the platform origin instead of from a created project. One notable thing: check_reqs isn't a .js file yet, as an API, it's check_reqs (*nix) and check_reqs + something from %PATHEXT% (Windows
Re: [Vote] Tools Release
Voting +1 * Verified signatures and hashes * Verified tags * Ability to install/uninstall Cordova * Ability to update Cordova * Ability to create blank app for Windows, WP8, Android * Ability to run apps * Reviewed release notes On 4/16/15, 1:24 PM, Steven Gill stevengil...@gmail.com wrote: Please review and vote on this Tools Release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-8859 Tools have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8859/ I have also uploaded these packages to npm under the rc tag for testing purposes. Test with npm install -g cordova@rc The packages were published from their corresponding git tags: cordova-js: 3.9.0 (17a3450e15) cordova-lib: 5.0.0 (cbd2a1e98d) cordova-plugman: 0.23.1 (8b9a73f6d4) cordova-cli: 5.0.0 (6c21fa85d0) Upon a successful vote I will upload the archives to dist/, publish them to NPM, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ran tests and built a hello world project, added a plugin. Ran mobile spec - 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
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 dmitry.blot...@gmail.com 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#connecting-t o-apaches-master https://github.com/apache/cordova-medic/blob/master/SLAVES.md#connecting- 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
RE: [VOTE] Plugins Release
+1 vote * Verified signatures and hashes * Verified tags * Verified plugins added correctly to blank * Verified blank app can be successfully ran and built for * Ran smoke testing of mobilespec app * Performed manual ad-hoc testing * Verified Release Notes -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Wednesday, April 15, 2015 4:25 PM To: dev@cordova.apache.org Subject: [VOTE] Plugins Release Please review and vote on the release of this plugins release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-8858 The plugins have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8858/ The packages were published from their corresponding git tags: cordova-plugin-battery-status: 1.0.0 (21ac0286c1) cordova-plugin-camera: 1.0.0 (d10bf50c61) cordova-plugin-console: 1.0.0 (293a261bac) cordova-plugin-contacts: 1.0.0 (e95ba2e805) cordova-plugin-device: 1.0.0 (a159702f79) cordova-plugin-device-motion: 1.0.0 (7a7b94e9a9) cordova-plugin-device-orientation: 1.0.0 (ec0f27f4ae) cordova-plugin-dialogs: 1.0.0 (6b06471ccc) cordova-plugin-file: 2.0.0 (9133873282) cordova-plugin-file-transfer: 1.0.0 (490063e1e5) cordova-plugin-geolocation: 1.0.0 (6dcc55b2a9) cordova-plugin-globalization: 1.0.0 (cc9c7c2113) cordova-plugin-inappbrowser: 1.0.0 (7d1b584306) cordova-plugin-media: 1.0.0 (12271f8633) cordova-plugin-media-capture: 1.0.0 (cd3a586252) cordova-plugin-network-information: 1.0.0 (30d51f8f32) cordova-plugin-splashscreen: 2.0.0 (d23ea4e011) cordova-plugin-statusbar: 1.0.0 (261f9576fe) cordova-plugin-test-framework: 1.0.0 (a2b4871a02) cordova-plugin-vibration: 1.0.0 (894310ecfb) Upon a successful vote I will upload the archives to dist/, upload them to npm, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ran mobile spec on Android and iOS - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Cordova TOOLS release - 4.3.1
Now that Cordova Android vote is complete, should we look at doing a TOOLS release with that included ? -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Monday, April 13, 2015 11:08 AM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Cordova TOOLS release - 4.3.1 Wanted to ping this thread again. Should we go ahead with the tools release that will take in the plugins-to-npm change, and then do another one for Android ? -Original Message- From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] Sent: Thursday, April 9, 2015 11:55 AM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Cordova TOOLS release - 4.3.1 https://github.com/apache/cordova-lib/pull/205 has been merged in to fix CB-8807 this morning. I have updated the JIRA. https://github.com/apache/cordova-lib/pull/202 needs to be still looked at and merged. Anyone? Thanks, Nikhil -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Thursday, April 9, 2015 6:26 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova TOOLS release - 4.3.1 I agree fix CB-8807 first, I think is a regression. On Wed, Apr 8, 2015 at 5:09 AM, Vladimir Kotikov (Akvelon) v-vlk...@microsoft.com wrote: Guys, there is a PR [1] to cordova-lib which could be a good candidate to be included in this release. [1] https://github.com/apache/cordova-lib/pull/205 --- Best regards, Vladimir -Original Message- From: Mark Koudritsky [mailto:kam...@google.com] Sent: Wednesday, 8 April, 2015 1:15 To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova TOOLS release - 4.3.1 +1 for a quick tools release. On Tue, Apr 7, 2015 at 12:34 PM, Steven Gill stevengil...@gmail.com wrote: Yeah, android 4.0 would be minor bump for cli according to our versioning strategy. So it could be 5.1.0. It would be nice to include it in 5 though so it can jump on the visibility 5 will create. Marketing! - corporate Steve P.S. I'm fine with releasing Cli 5.0 without android 4.0 if that is what people want. On Apr 7, 2015 8:40 AM, Michal Mocny mmo...@chromium.org wrote: +1 to 5.0.0. Will Android bump to 4.0 mean cli major rev? I +think it would just be a minor, no? -Michal On Mon, Apr 6, 2015 at 5:45 PM, Steven Gill stevengil...@gmail.com wrote: I'm thinking we should make this release cordova 5.0.0. It will be the first release with fetching from npm and encouraging developers do use the new plugin names. I think a plugins release should go out alongside it. It would be really nice if we could get android 4.0.0 released and pinned before it too but I won't hold my breath on this. On Mon, Apr 6, 2015 at 2:07 PM, Nikhil Khandelwal nikhi...@microsoft.com wrote: This is a good one to take in before release, since it changes config.xml schema: https://github.com/apache/cordova-lib/pull/202. It needs to be code reviewed. Thanks, Nikhil -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Monday, April 6, 2015 1:36 PM To: dev@cordova.apache.org Subject: [DISCUSS] Cordova TOOLS release - 4.3.1 Hi, In the recent days, a couple of platforms have released. We are also voting on Windows platform release. There have also been a couple of bug fixes in the CLI/Lib. Does it make sense to do a tools release ? Wanted to start a discuss thread on doing a TOOLS release. Are there other PRs that people want to get into this release ? -- -- - 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 -- Carlos Santana csantan...@gmail.com
Re: Proposal: Expose check_reqs at the CLI level
Carlos, you are right, check_reqs should be in the platform repo, CLI will
just proxy the call to the platforms.
On 4/13/15, 10:29 PM, Carlos Santana csantan...@gmail.com wrote:
+1 if check_reqs are kept in the platform repos, currently check_reqs is a
platform concerned
if it's available from CLI it will be just a proxy to the platform
check_reqs.
if don't keep it in the platform repo, and add this logic to cli repo, we
will need to maintained a list of reqs for each platform, for each version
of each platform.
This is the reason why it was removed from cli and just is present in the
platform repo/code
On Mon, Apr 13, 2015 at 5:13 PM, Josh Soref jso...@blackberry.com wrote:
I'm +1 for `cordova doctor` and `cordova platform doctor
{platformname}`.
The former should apply to all current platforms, the latter should
support
doctoring for available but not added platforms -- if said platform were
specified.
And we should note in the documentation or `cordova doctor` that it may
do
other checks -- e.g. linting the config.xml, warning about CSP, possibly
mentioning when a plugin is out of date -- just to indicate to people
that
the behavior may evolve.
Not that this is more or less fixing a regression that we introduced
when
we
made `cordova platform add` not call check_reqs.
-Original Message-
From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
Sent: Monday, April 13, 2015 2:53 PM
To: dev@cordova.apache.org
Subject: Proposal: Expose check_reqs at the CLI level
Hi,
One of the main problems a lot of developers seem to have is the
issue to
setting up their machines for building various platforms. This came
out
from
the Stack overflow survey, and the number of questions on stack
overflow,
twitter. Etc.
I thought it would be helpful to have a check_reqs command exposed at
the
CLI level. This is similar to `brew doctor` or `appium doctor`. The
idea
is
1. Have a way for the user to see if they have all dependencies
(like
JAVA_HOME or ANDROID_HOME) set up? This happens at build time, but
moving it out to a CLI level command where you can run cordova
check_reqs
(or something similar) would be useful to the users.
2. Today, the build command shows one error at a time. The
check_reqs
could run all the checks, and show a summary of the issues so that the
user
can fix them all, instead of fixing one, running build, fixing again,
etc.
What does the community think of this idea ? Can we implement a
prototype
and see if this is useful to our developers ?
Note that this does not change or break existing functionality - it
just
exposes
the already existing check_reqs in the CLI. Build will continue to
call
check_reqs.
Please vote on this proposal, or raise any concerns you may have.
--
Carlos Santana
csantan...@gmail.com
-
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 you raise an interesting point on the behavior of check_reqs for
platform that are not yet added.
The options, as you mention are
Question 1
1 - Add the platform, run check_reqs script, remove the platform and report
results.
1.5 - Just download the check_reqs script (or use it from the cached platform
directory) without adding the platform, and run that.
2 - Just say that platform is not added, so cannot check requirements.
Question 2: It also comes to the case of - when would a user want to run the
requirement check
- before starting a cordova project ?
- before adding a platform ?
- should the requirements be checked when a platform is added, or when it is
built ?
The answer to the above questions will help us understand if a top level
req_check is required or not. We should also look at what check_reqs do today -
the do not tell you ALL the missing pieces for building an SDK.
It would be good to hear what the others in the community think about these
answers.
-Original Message-
From: Josh Soref [mailto:jso...@blackberry.com]
Sent: Tuesday, April 14, 2015 9:55 AM
To: dev@cordova.apache.org
Subject: RE: Proposal: Expose check_reqs at the CLI level
Fwiw, for the case of a platform that isn't in a project yet, I'd envision:
`cordova platform doctor not-yet-installed`
to do effectively:
```sh
(
PLATFORM=not-yet-installed
(cordova platform add $PLATFORM 21) /dev/null
cordova platform doctor $PLATFORM;
(cordova platform remove $PLATFORM 21)
)
```
i.e. add the platform (or create a temporary project, and add the platform
to the temporary project), and then run platform doctor, and then remove the
platform (and if it was in a temporary project, delete the temporary
project...).
I don't really want to expos a 'check_reqs' verb via CLI.
If we really really want to, we could have `cordova platform requirements
[PLATFORM...]` as a verb, that's ok.
If someone wants to call `check_reqs` directly, they're welcome to do so,
but it's an incredibly ugly thing and doesn't belong in a public facing
interface.
-Original Message-
From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
Sent: Tuesday, April 14, 2015 10:19 AM
To: dev@cordova.apache.org
Subject: Re: Proposal: Expose check_reqs at the CLI level
Carlos, you are right, check_reqs should be in the platform repo, CLI will
just proxy the call to the platforms.
On 4/13/15, 10:29 PM, Carlos Santana csantan...@gmail.com wrote:
+1 if check_reqs are kept in the platform repos, currently check_reqs is
a
platform concerned
if it's available from CLI it will be just a proxy to the platform
check_reqs.
if don't keep it in the platform repo, and add this logic to cli repo, we
will need to maintained a list of reqs for each platform, for each
version
of each platform.
This is the reason why it was removed from cli and just is present in the
platform repo/code
On Mon, Apr 13, 2015 at 5:13 PM, Josh Soref jso...@blackberry.com
wrote:
I'm +1 for `cordova doctor` and `cordova platform doctor
{platformname}`.
The former should apply to all current platforms, the latter should
support
doctoring for available but not added platforms -- if said platform
were
specified.
And we should note in the documentation or `cordova doctor` that it may
do
other checks -- e.g. linting the config.xml, warning about CSP,
possibly
mentioning when a plugin is out of date -- just to indicate to people
that
the behavior may evolve.
Not that this is more or less fixing a regression that we introduced
when
we
made `cordova platform add` not call check_reqs.
-Original Message-
From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com]
Sent: Monday, April 13, 2015 2:53 PM
To: dev@cordova.apache.org
Subject: Proposal: Expose check_reqs at the CLI level
Hi,
One of the main problems a lot of developers seem to have is the
issue to
setting up their machines for building various platforms. This came
out
from
the Stack overflow survey, and the number of questions on stack
overflow,
twitter. Etc.
I thought it would be helpful to have a check_reqs command exposed at
the
CLI level. This is similar to `brew doctor` or `appium doctor`. The
idea
is
1. Have a way for the user to see if they have all dependencies
(like
JAVA_HOME or ANDROID_HOME) set up? This happens at build time, but
moving it out to a CLI level command where you can run cordova
check_reqs
(or something similar) would be useful to the users.
2. Today, the build command shows one error at a time. The
check_reqs
could run all the checks, and show a summary of the issues so that
the
user
can fix them all, instead of fixing one, running build, fixing again,
etc.
What does the community think of this idea ? Can we implement a
prototype
and see if this is useful to our developers ?
Note
Proposal: Expose check_reqs at the CLI level
Hi, One of the main problems a lot of developers seem to have is the issue to setting up their machines for building various platforms. This came out from the Stack overflow survey, and the number of questions on stack overflow, twitter. Etc. I thought it would be helpful to have a check_reqs command exposed at the CLI level. This is similar to `brew doctor` or `appium doctor`. The idea is 1. Have a way for the user to see if they have all dependencies (like JAVA_HOME or ANDROID_HOME) set up? This happens at build time, but moving it out to a CLI level command where you can run cordova check_reqs (or something similar) would be useful to the users. 2. Today, the build command shows one error at a time. The check_reqs could run all the checks, and show a summary of the issues so that the user can fix them all, instead of fixing one, running build, fixing again, etc. What does the community think of this idea ? Can we implement a prototype and see if this is useful to our developers ? Note that this does not change or break existing functionality - it just exposes the already existing check_reqs in the CLI. Build will continue to call check_reqs. Please vote on this proposal, or raise any concerns you may have.
Re: cordova-vm.apache.org
If we still have the machine, we could still use it. I think we are still working on getting CouchDB setup on Apache, or we could use this as a slave. On 4/8/15, 8:35 AM, Andrew Grieve agri...@chromium.org wrote: We got a VM a while ago with the idea to use it for BuildBot / cordova-docs ruby environment. I don't think either of these are still applicable (http://ci.cordova.io is *awesome*!!!) Any reason to not ask for it to be decommissioned? - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: proposed utility
Looks like a good candidate to discuss at the monthly hangouts ? -Original Message- From: Staci Cooper [mailto:staci@gmail.com] Sent: Wednesday, April 8, 2015 11:05 AM To: dev@cordova.apache.org Subject: Re: proposed utility Did anything ever come of this? I'd be happy to do some work on this if the consensus is that the implementation needs to be changed. On Tue, Jan 13, 2015 at 2:10 PM, Staci Cooper staci@gmail.com wrote: When I was implementing this I initially did add it as a '--local / -l' option to the cli. My concern was that it requires the developer to have a global installation of Cordova even if all they want is the local command. And assuming the user's global and local installs have different version numbers, all they would have to do is accidentally omit the -l and they would unwittingly use the wrong version of Cordova. I could add it back in as a flag, or have separate 'cordova' and 'cordova-local' commands in the cli. Or were you suggesting changing the default behavior of the cordova command to shell out to local? In which case we could have a flag to turn that behavior off for backwards compatibility... or to fallback to the global version if no local version is found. Hm, I'm not sure.. On Fri, Jan 9, 2015 at 4:35 PM, Jesse purplecabb...@gmail.com wrote: Do we need to start a discussion around cordova-cli plugins? Personally I prefer keeping this in a separate repo. @purplecabbage risingj.com On Fri, Jan 9, 2015 at 1:08 PM, Tommy Williams to...@devgeeks.org wrote: Just as an aside, I have resorted to: alias cdv=./node_modules/.bin/cordova Heh. On 10/01/2015 8:06 am, Tommy Williams to...@devgeeks.org wrote: +1 for what Michal describes. Better going forward as well as backwards compatibility. Win win? On 10/01/2015 7:54 am, Michal Mocny mmo...@chromium.org wrote: I like the way gulp works: the same package acts different when installed globally/locally. Namely, the global always shells work off to the local. So, instead of a separate cordova-local utility (akin to grunt and grunt-cli), perhaps we just add your feature directly into cordova-cli? For backwards compat, I think we should still allow the global cordova-cli to do work as we do now (i.e. we don't *require* local installs), but if a local install happens to exist it would shell out to that. Anyway, neat that you've implemented this already! On Fri, Jan 9, 2015 at 3:41 PM, Staci Cooper staci@gmail.com wrote: A while ago I made a utility called cordova-local for managing multiple local Cordova installations. It's similar to how grunt/grunt-cli works; once installed globally, you run 'cordova-local' instead of 'cordova' and it will locate and pass its arguments off to the closest installation. It's kept and installed independently of the cli but my initial idea was to keep it in the cordova-cli repo. Since that would complicate the tools-release/versioning process I closed that PR and would like to propose including it as a new repo. I added some specs and docs and put it in a utilities repo that could be used for similar cli-independent tools, currently here: https://github.com/stacic/cordova-utility. I added some tests to it and also made PRs for documenting the utility in cordova-docs https://github.com/apache/cordova-docs/pull/259 and adding it to the tools release in cordova-coho https://github.com/apache/cordova-coho/pull/61. Opinions? Concerns?
Re: Platform guides update
I also think that apart for API/Reference like docs, it may help the community to have detailed guide, tutorials, etc. I understand that some of them may be hard, but do you guys see value in putting up something like a ³course² for using Cordova, tutorial for building sample apps, using Cordova with JS frameworks, etc - things that would help a beginner get started quickly. On 4/7/15, 1:41 PM, Raymond Camden raymondcam...@gmail.com wrote: Fair enough. I think my concern is overwhelming new users - but - I'll stand back and wait for these new docs to go up before I complain/nag anymore. :) On Tue, Apr 7, 2015 at 3:34 PM, Brian LeRoux b...@brian.io wrote: I humbly submit that we want very detailed documentation to turn those lower numbers into more involved community members. (Ideally contributing code and docs themselves!) On Tue, Apr 7, 2015 at 1:24 PM, Raymond Camden raymondcam...@gmail.com wrote: That makes sense - I just worry that if that use case (extending Cordova) is 10% of the reader base than it should not (imo) be 50% of the docs. Btw - totally guessing at those numbers as I haven't seen the changes. :) On Tue, Apr 7, 2015 at 2:58 PM, Brian LeRoux b...@brian.io wrote: We recommend using the thing that works best for you for building apps BUT if you are extending Cordova you'll need to run with Android Studio, Xcode and friends. We support both. On Tue, Apr 7, 2015 at 12:47 PM, Raymond Camden raymondcam...@gmail.com wrote: Replace Eclipse example w/ Android Studio as officially recommended option/tool Do we really recommend this over CLI + your favorite editor ? On Tue, Apr 7, 2015 at 2:35 PM, Jesse purplecabb...@gmail.com wrote: +1000 @purplecabbage risingj.com On Tue, Apr 7, 2015 at 12:31 PM, Andrew Grieve agri...@chromium.org wrote: These changes all sound great! On Tue, Apr 7, 2015 at 3:01 PM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Hi guys, I see that some docs are outdated or not actual anymore so I want to improve this. Please let me know if someone already working on this or going to take a look. I've listed below some things I want to update, could you please review them before I stared working on this (additional suggestions and ideas are very welcome) iOS: 1. Xcode 4.x-5.x 2. Add information about ios-sim required to deploy app from command line 3. Add information how to list available deploy targets and run app on specific target/device Android: 1. Add changes in favor of replacing Ant w/ Gradle a. Remove Ant from requirements b. Replace Eclipse example w/ Android Studio as officially recommended option/tool 2. Add more details about particular Android packages/components required to be installed. Android 5.0.1 (API 21) platform SDK Android SDK Build-tools version 19.1.0 or higher Android Support Repository (Extras) 3. Add information how to list available deploy targets and run app on specific target/device Windows: 1. Remove 'To develop apps for Windows 8.0 only:' 2. Hardware requirements to run Windows Phone emulator (Client Hyper-V and Second Level Address Translation (SLAT)) 3. Add information how to list available deploy targets and run app on specific target/device Thx! Sergey - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org -- === Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org -- === Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org -- == = Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcam...@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail:
RE: [VOTE] 3.8.1 Windows Release
Voting +1 * Verified archives via `coho verify-archive` * Verified tags manually * Verified blank app creates correctly with platform * Verified blank app can be successfully run and built * Checked whitespace issues * Checked Unicode issues * Ran smoke testing of mobilespec app (ran autotests) * Verified compatibility with core plugins -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Friday, April 3, 2015 4:15 PM To: dev@cordova.apache.org Subject: [VOTE] 3.8.1 Windows Release Please review and vote on this 3.8.1 Windows Release. Release issue: https://issues.apache.org/jira/browse/CB-8796 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8796 The package was published from its corresponding git tag: cordova-windows: 3.8.1 (9b003319c6) Upon a successful vote I will upload the archive to dist/, and publish it to NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Cordova Monthly Hangouts - April Edition
Closing this poll - looks like Apr 10 (Friday) 1:00 pm EST has the max possible folks. Let us schedule the hangout for April 10, at 1:00 pm EST. Can someone help with creating the Agenda document ? We will be sharing the hangouts link closer to the poll. -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Friday, April 3, 2015 9:46 AM To: dev@cordova.apache.org Subject: RE: Cordova Monthly Hangouts - April Edition Bumping this thread up one last time. Will close the results for the hangout, and send out a date later today PST. -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Thursday, April 2, 2015 3:04 PM To: dev@cordova.apache.org Subject: Cordova Monthly Hangouts - April Edition Wanted to bump up the thread about Cordova hangouts. We have 10 responses so far. I plan to close the poll early tomorrow morning so that we have enough time to schedule the hangout and folks can make it. If you have not yet responded to the time, please add your preference here http://doodle.com/kydhnyzzwge92hsu - 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: Cordova Monthly Hangouts - April Edition
Bumping this thread up one last time. Will close the results for the hangout, and send out a date later today PST. -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Thursday, April 2, 2015 3:04 PM To: dev@cordova.apache.org Subject: Cordova Monthly Hangouts - April Edition Wanted to bump up the thread about Cordova hangouts. We have 10 responses so far. I plan to close the poll early tomorrow morning so that we have enough time to schedule the hangout and folks can make it. If you have not yet responded to the time, please add your preference here http://doodle.com/kydhnyzzwge92hsu - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Cordova Monthly Hangouts - April Edition
Wanted to bump up the thread about Cordova hangouts. We have 10 responses so far. I plan to close the poll early tomorrow morning so that we have enough time to schedule the hangout and folks can make it. If you have not yet responded to the time, please add your preference here http://doodle.com/kydhnyzzwge92hsu
Re: [Vote] 3.8.0 WP8 Release (Attempt 2)
Voting +1 * Verified archives via 'coho verify-archive' * Verified tags manually * Verified platform version * Verified blank app creates correctly with platform * Verified blank app can be successfully run and built * Checked whitespace issues * Checked Unicode issues * Ran smoke testing of mobilespec app (ran autotests) On 3/31/15, 3:10 PM, Steven Gill stevengil...@gmail.com wrote: Please review and vote on this 3.8.0 WP8 Release. Release issue: https://issues.apache.org/jira/browse/CB-8748 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8748 The package was published from its corresponding git tag: cordova-wp8: 3.8.0 (dcd035bed4) Upon a successful vote I will upload the archive to dist/ and publish it to NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Add Windows on OSX system fails in cordova 4.3 (window 3.8)
+1 to start a 3.8.1 We will also have a bunch of platforms that would have released, so we could do a CLI release too. On 4/1/15, 2:40 PM, Jesse purplecabb...@gmail.com wrote: Might as well start a 3.8.1 release for this, I think it is worth it. @purplecabbage risingj.com On Wed, Apr 1, 2015 at 2:29 PM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Just tried and confirm this has been fixed in master after release. -Sergey -Original Message- From: Sergey Grebnov (Akvelon) Sent: Wednesday, April 1, 2015 10:53 PM To: dev@cordova.apache.org Subject: RE: Add Windows on OSX system fails in cordova 4.3 (window 3.8) Hi Jeff, I think this was fixed after release: https://github.com/apache/cordova-windows/commit/030be05e7fc83408bcf5a74f 05ab7a0a6ca335aa I'll be able to try and report back later today, but if you want try it yourself: cordova platform add https://github.com/apache/cordova-windows.git -Sergey -Original Message- From: Jeff Burtoft [mailto:jeffb...@microsoft.com] Sent: Wednesday, April 1, 2015 8:43 PM To: dev@cordova.apache.org Subject: Add Windows on OSX system fails in cordova 4.3 (window 3.8) Hi, Is anyone else having a problem adding Windows platform on an OSX machine Rupert:WATDocs fernando$ cordova platform add windows WARNING: Applications for platform windows can not be built on this OS - darwin. Adding windows project... Error: /Users/fernando/.cordova/lib/npm_cache/cordova-windows/3.8.0/package/bin/ create: Command failed with exit code EACCES at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova /superspawn.js:131:23) at ChildProcess.emit (events.js:95:17) at Process.ChildProcess._handle.onexit (child_process.js:818:12) I'm not trying to build it, only create the package. Am I doing something wrong or is this a bug? Thanks, Jeff Jeff Burtoft * Developer Experience * Web Apps - 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: [Vote] 3.8.0 WP8 Release
+1 on the vote. -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Thursday, March 26, 2015 3:54 PM To: dev@cordova.apache.org Subject: [Vote] 3.8.0 WP8 Release Please review and vote on this 3.8.0 WP8 Release. Release issue: https://issues.apache.org/jira/browse/CB-8748 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8748 The package was published from its corresponding git tag: cordova-wp8: 3.8.0 (6e319c9828) Upon a successful vote I will upload the archive to dist/ and publish it to NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [Discuss] Deprecate platform Windows 8.0
+1 on deprecation to the platform. I think we should also ensure that all plugins now refer to Windows instead of windows8 platform. -Original Message- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Friday, March 20, 2015 1:39 PM To: dev@cordova.apache.org Subject: Re: [Discuss] Deprecate platform Windows 8.0 cordova-windows contains code for windows universal apps ( windows 8.1 and wp8.1 ) It also contains legacy support for windows8.0 To target wp8.1 you : cordova platform add windows # deploy app to Windows Phone 8.1 emulator cordova run windows -- --phone # deploy app to connected device cordova run windows --device -- --phone @purplecabbage risingj.com On Fri, Mar 20, 2015 at 11:35 AM, Carlos Santana csantan...@gmail.com wrote: Jesse which is the platform repo for the windows universal? I always get those mixed. Can I assume there is only one platform for windows universal to support windows 8.1 and windows phone 8.1? And lastly if I wan to try windows universal which one is the key name for cordova cli? cordova platform add window ? sorry for all the stupid questions, it's being a while since I worked on windows. On Thu, Mar 19, 2015 at 4:26 PM, Jesse purplecabb...@gmail.com wrote: The time is long past, and we should clean this out of our codebase soon. Windows 8.1 is better and offers better support. It's a free upgrade to anyone who has Windows 8.0, it will install on any device that supports 8.0, and it has been out for almost 18 months. Any objections? @purplecabbage risingj.com -- Carlos Santana csantan...@gmail.com
RE: Cordova Monthly Hangouts
Carlos, you did not miss it, still working on scheduling it :) Here is the doddle - please respond to this and indicate your availability. Since the hangouts usually go to 2 hours, and to keep the number of options sane in doddle, I put up 2 hour slots. Let me know if we should make it 1 hour slots. Here is the participation link - http://doodle.com/kydhnyzzwge92hsu -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Thursday, March 26, 2015 9:58 AM To: dev@cordova.apache.org Subject: Re: Cordova Monthly Hangouts +1 did I missed the hangout? I would like to attend. Micha I like the new term npm-ness :-) Yes Android 4.0 is important for us, we are about to start new work and want to start with a released one. On Tue, Mar 24, 2015 at 7:01 PM, tommy-carlos williams to...@devgeeks.org wrote: +1 for package.json discussions -- tommy-carlos williams On 25 March 2015 at 09:18:12, Michal Mocny (mmo...@chromium.org) wrote: Another topic is discussion of package.json based cli workflow, aka leveraging more npm-ness in our tools. -Michal On Tue, Mar 24, 2015 at 1:59 PM, Andrew Grieve agri...@chromium.org wrote: +1! On Tue, Mar 24, 2015 at 1:23 PM, Jesse purplecabb...@gmail.com wrote: +1 asap, thanks Parash! We are much more coherent when we meet. On Mar 24, 2015, at 10:02 AM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Hi, I was wondering if folks would be interested in doing a hangout to quickly resolve some of the outstanding issues that we have been talking on the mailing list. I think we could talk about the following * Androind 4.0 release * Medic/ParaMedic/Mobile Spec - progress and next steps * Finalize Save/Restore discussions * ApacheCon ? I can volunteer to help set this up if we think there are items that we would like to discuss and close on. -- --- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org -- Carlos Santana csantan...@gmail.com
RE: [VOTE] Cordova-Plugin-Whitelist and Cordova-Plugin-Legacy-Whitelist Plugins Release
Should we have to restart the vote thread, now that the tag will change ?
-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, March 26, 2015 7:41 AM
To: dev
Subject: Re: [VOTE] Cordova-Plugin-Whitelist and
Cordova-Plugin-Legacy-Whitelist Plugins Release
That'd be pretty sad if it were expected :P.
Totally my bad on this one. I've committed a fix.
On Thu, Mar 26, 2015 at 9:40 AM, Alexander Sorokin (Akvelon)
v-als...@microsoft.com wrote:
Hi guys,
I am getting the following error when trying to build a project with
legacy-whitelist plugin installed for android@4.0.0-dev:
C:\Projects\Cordova\mobspec-android\platforms\android\src\org\apache\cordova\whitelist\LegacyWhitelistPlugin.java:44:
error: cannot find symbol
public void handleStartTag(XmlPullParser xml) {
^
symbol: class XmlPullParser
C:\Projects\Cordova\mobspec-android\platforms\android\src\org\apache\cordova\whitelist\LegacyWhitelistPlugin.java:68:
error: cannot find symbol
public void handleEndTag(XmlPullParser xml) {
^
symbol: class XmlPullParser
Is this expected?
Thanks,
Alexander Sorokin
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, March 25, 2015 23:23
To: dev@cordova.apache.org
Subject: [VOTE] Cordova-Plugin-Whitelist and
Cordova-Plugin-Legacy-Whitelist Plugins Release
Please review and vote on the releases of cordova-plugin-whitelist and
cordova-plugin-legacy-whitelist plugins.
Release issue: https://issues.apache.org/jira/browse/CB-8739
The plugins have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8739/
The packages were published from their corresponding git tags:
cordova-plugin-whitelist: 1.0.0 (38f5a9fa2c)
cordova-plugin-legacy-whitelist: 1.0.0 (b4e1b3726a)
Upon a successful vote I will upload the archives to dist/ and upload
them to npm.
Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting
.md
Voting will go on for a minimum of 48 hours.
I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] cordova-wp8 + Newtonsoft.JSON
I think we can use option 4 - distributing DLLs of third party software is fine - we only need to ensure that it is clean from an IP perspective. I think 4 is the best option as you said, and we could ask the author of the library about any potential patent issues. I also think that Apache puts the due diligence of IP and patent responsibility on the committers -Original Message- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Thursday, March 26, 2015 11:05 AM To: dev@cordova.apache.org Subject: [DISCUSS] cordova-wp8 + Newtonsoft.JSON We have several options, of varying difficulty, legal responsibility, risk, and technical debt. 1. Redistribute Newtonsoft.JSON (NJ) source code as part of every new cordova-wp8 project - it's a lot of code to add to the project, more that cordova-wp8 itself - we completely control our dependencies and will never fall out of sync 2. Redistribute NJ source as part of the library and have every new cordova-wp8 project link to it. - some added complexity, but technically sound, and not as wasteful seeming as #1 - we could have issues with dependencies if NJ included source changes between cordova-wp8 versions 3. Redistribute NJ source, build it when cordova-wp8 is installed on the users machine, add the .dll to every new cordova-wp8 project. - same issues/benefits as #2, some added complexity 4. Redistribute NJ as a pre-built dll and as part of the wp8 template. - I like this best, but we have to dig through legal some more. 5. Do some magic with nuget dependencies so VS will download it. - lots of unknowns ( to me, others may know more ) - can only create cordova-wp8 projects when online ( Android already has this restriction ) 6. Redistribute NJ as a cordova-wp8 plugin and make it a dependency of cordova-wp8 - a little awkward, but doable 7. Do nothing - realistically wp8 should be deprecated soon, wp8.1 has much more to offer, and win10 is on the horizon. We could just let the sun set. @purplecabbage risingj.com
RE: [DISCUSS] Cordova-WP8 Release 3.8.0
About the JSON library, as I understand, only ASF libraries need to be included in source form - third party libraries can still be binaries, and we would just need to ensure that it does not have IP issues. http://www.apache.org/legal/resolved.html Hence, I think we can include the JSON library. -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Wednesday, March 25, 2015 1:34 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-WP8 Release 3.8.0 https://issues.apache.org/jira/browse/CB-8748 On Wed, Mar 25, 2015 at 1:18 PM, Jesse purplecabb...@gmail.com wrote: Yeah, let's push out a 3.8.0 for cordova-wp8 We can do a 4.0.0 after I get the JSON fixes in. @purplecabbage risingj.com On Tue, Mar 24, 2015 at 2:36 PM, Rob Paveza rob.pav...@microsoft.com wrote: Is it worth breaking out the Newtonsoft.Json additions into a separate (major 4.0) release and taking these bugfixes into a minor release until we get the legal stuff worked out on the JSON side? -Original Message- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Tuesday, March 24, 2015 11:19 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-WP8 Release 3.8.0 I would like to finish off the Newtonsoft.Json additions, and release a 4.0.0 The changes to the JSON namespace in c# potentially break some plugins. The barcode scanner [1] for one, as it is including the dll already. There is also possibly some impact on the file-transfer plugin [2] however, that is not a breaking change. [1] https://github.com/phonegap-build/PushPlugin [2] https://github.com/apache/cordova-plugin-file-transfer/blob/master/src /wp/FileTransfer.cs#L319 @purplecabbage risingj.com On Tue, Mar 24, 2015 at 10:26 AM, Rob Paveza rob.pav...@microsoft.com wrote: It's been three months since the last release of Cordova-WP8. There are a number of bugfixes pending, particularly with emulator vs. deploy-to-device and in scenarios where there are only Phone 8.1 tools on the machine doing the building. Also added JSHint, improved console logging, etc. There is the outstanding issue is that of Newtonsoft.Json (and a thread going on about it), but if we can nail that down today either way, we can move this along to a vote tomorrow. Any other outstanding issues to discuss? -Rob - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Cordova Monthly Hangouts
Hi, I was wondering if folks would be interested in doing a hangout to quickly resolve some of the outstanding issues that we have been talking on the mailing list. I think we could talk about the following * Androind 4.0 release * Medic/ParaMedic/Mobile Spec - progress and next steps * Finalize Save/Restore discussions * ApacheCon ? I can volunteer to help set this up if we think there are items that we would like to discuss and close on.
Re: [VOTE] Camera Plugin Release 0.3.6
Voting + 1 €Verified signatures and hashes €Verified tags €Verified plugins added correctly to blank app €Verified blank app can be successfully ran and built €Ran smoke testing of mobilespec app (ran autotests) €Performed manual ad-hoc testing €Verified Release Notes On 3/10/15, 5:26 PM, Steven Gill stevengil...@gmail.com wrote: Please review and vote on the release of this Camera plugin release. Release issue: https://issues.apache.org/jira/browse/CB-8646 The plugins have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8646/ The packages were published from their corresponding git tags: cordova-plugin-camera: 0.3.6 (00cd249dd7) Upon a successful vote I will upload the archives to dist/, upload them to the Plugins Registry NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [Vote] 3.8.0 Cordova App Hello World Release
Voting +1 for this. Also did initial tests on Windows, seems to work • Verified signatures and hashes • Verified tags • Verified that app can be built and ran under windows, wp8 and android platforms • Verified release notes: + added license header to config.xml + added releasenotes.md + removed version file, package.json can keep track of version + Adding hooks to default app + [CB-8597] First attempt at importing cordova-app-hello-world via npm dependency + Remove jasmine ref + Tweak CSP string + CB-8295 Add content-security-policy meta to template + Remove target-density and height=device-height from viewport + Remove self-closing slashes from meta since this isn't xhtml -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Wednesday, March 11, 2015 7:16 AM To: dev Subject: Re: [Vote] 3.8.0 Cordova App Hello World Release Note that this pulls in the addition of a content-security-policy meta tag. Please ensure that this doesn't break your platform when voting. On Tue, Mar 10, 2015 at 7:30 PM, Steven Gill stevengil...@gmail.com wrote: Please review and vote on this 3.8.0 Cordova App Hello World Release. Release issue: https://issues.apache.org/jira/browse/CB-8645 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8645 The package was published from its corresponding git tag: cordova-app-hello-world: 3.8.0 (0b55140d09) Upon a successful vote I will upload the archive to dist/ and publish it to NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting .md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Built a hello world app using the CLI
RE: [Vote] 3.8.0 Cordova App Hello World Release
I think if we change the tag, we will have to vote again. However, we don’t have to necessarily wait for 72 hours, for a fix that is small. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Wednesday, March 11, 2015 6:18 PM To: dev Subject: Re: [Vote] 3.8.0 Cordova App Hello World Release -1 Verified it works on the latest release iOS and Android, but I had a typo in the CSP string: https://github.com/apache/cordova-app-hello-world/commit/18fc9b4eaecd90bf35795c31a7801bc5260b5c6c Perhaps we could re-spin with this one fix and leave the vote end period the same (assuming everyone can still verify based on this one-character change)? On Wed, Mar 11, 2015 at 2:13 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Voting +1 for this. Also did initial tests on Windows, seems to work • Verified signatures and hashes • Verified tags • Verified that app can be built and ran under windows, wp8 and android platforms • Verified release notes: + added license header to config.xml + added releasenotes.md + removed version file, package.json can keep track of version + Adding hooks to default app + [CB-8597] First attempt at importing cordova-app-hello-world via npm dependency + Remove jasmine ref + Tweak CSP string + CB-8295 Add content-security-policy meta to template + Remove target-density and height=device-height from viewport + Remove self-closing slashes from meta since this isn't xhtml -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Wednesday, March 11, 2015 7:16 AM To: dev Subject: Re: [Vote] 3.8.0 Cordova App Hello World Release Note that this pulls in the addition of a content-security-policy meta tag. Please ensure that this doesn't break your platform when voting. On Tue, Mar 10, 2015 at 7:30 PM, Steven Gill stevengil...@gmail.com wrote: Please review and vote on this 3.8.0 Cordova App Hello World Release. Release issue: https://issues.apache.org/jira/browse/CB-8645 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8645 The package was published from its corresponding git tag: cordova-app-hello-world: 3.8.0 (0b55140d09) Upon a successful vote I will upload the archive to dist/ and publish it to NPM. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voti ng .md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Built a hello world app using the CLI
Re: [Discuss] Camera plugin release
+1 to making this release. On 3/9/15, 4:51 PM, Steven Gill stevengil...@gmail.com wrote: Saw a thread last week about camera plugin needing a release. Going to start this tomorrow if we don't have any objections - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [Vote] Tools Release February 27, 2015
Since this isn't a blocker, I am going to move ahead with completing this vote thread and finishing off this plugins release. You mean tools release, right ? -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Monday, March 2, 2015 2:30 PM To: dev@cordova.apache.org Subject: Re: [Vote] Tools Release February 27, 2015 So I push a commit to master that adds defaults.json to npmignore. defaults.json is generated based on a plugin.xml every time the createpackagejson command is run. It won't cause any issues having it bundled but it is better to not have it in. Since this isn't a blocker, I am going to move ahead with completing this vote thread and finishing off this plugins release. On Mon, Mar 2, 2015 at 10:34 AM, Andrew Grieve agri...@chromium.org wrote: Awesome. So long as it's seems alright to you Steve, then I vote +1. On Mon, Mar 2, 2015 at 11:26 AM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Voting +1 * Verified signatures and hashes. Passed * Verified tags manually. Passed * Ability to install/uninstall Cordova. Passed * Ability to update Cordova. Passed * Ability to create blank app for Windows, WP8, Android. Passed * Ability to run apps. Passed * Reviewed release notes (Passed): plugman: CB-8416 added plugman createpackagejson . command to generate a package.json file from plugin.xml CB-8370 Update documentation for plugman publish without args cordova-lib CB-8472 Can't find config.xml error installing browser platform after plugin. (close #167) CB-8239 Fix cordova platform add PATH when PATH is relative and CWD != project root CB-8227 CB8237 CB-8238 Add --save flag and autosave to 'cordova platform add', 'cordova platform remove' and 'cordova platform update' CB-8239 Fix platform update should ignore cdv:engine (close #159) CB-8416: added plugman createpackagejson . command to create a package.json from plugin.xml CB-6973 add spec-plugman to npm run jshint CB-6973 fix spec-plugman jshint failures CB-8377 Fixed tag parsing (close #156) CB-8370 Make plugman publish without args default to CWD CB-8366 android: Remove empty `framework` directory upon uninstall CB-6973 Enable JSHint for spec-cordova CB-8239 Add support for git urls to 'cordova platform add' (close #148) CB-8358 Add `--link` for `platform add` and `platform update` CB-6973 remove base rules from individual files in src. CB-6973 have base rules in .jshintrc file. CB-8168 --list support for cordova-lib (close #145.) Chnage plugman test plugins to have IDs as directory names Make all test plugin IDs unique Empty out contents of plugin test files (and delete some unused ones) CB-8285 Don't create .fetch.json files within plugin directories CB-8286 Never persist value of create --link-to within .cordova/config.json CB-8153 generate cordova_plugins.json for browserify based projects CB-8244 android: Have `plugin add --link` create symlinks for `source-file`, `framework`, etc. CB-8226 'cordova platform add' : Look up version in config.xml if no version specified Delete root .npmignore, since there's no node module there cordova-js CB-8302 Added npm test script CB-8300 Added CI configuration files cordova-cli docs update for plugin --save CB-8439 Fix 'cordova platform update' documentation to include `plat-spec` (close #208) CB-8379 Have --version print out cordova-lib version if it's not the same as CLI's version CB-8211, CB-8358 Update `--link` help text CB-8168 --list support for CLI (close #205) CB-8227 CB-8237 CB-8238 Add --save option to 'cordova platform add', 'cordova platform remove' and 'cordova platform update' CB-5316 Spell Cordova as a brand unless it's a command or script CB-7739 document installing specific version of platforms On 3/2/15, 8:02 AM, Steven Gill stevengil...@gmail.com wrote: I have defaults.json in gitignore so it doesn't get checked in. It is a mistake to have in there. Definitely would be better to write it to some temp directory outside of source. I'll see if it causes problems. Hopefully it doesn't block release and we can just fix on master. I'll report back. On Mar 2, 2015 7:51 AM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: I vote +1: * Verified tools installation on windows * Verified new blank app could be created on windows * Verified android, ios, windows and wp8 platforms could be added, built and run. Thx! Sergey -Original Message- From: Mefire O. [mailto:ommen
Re: [Vote] Tools Release February 27, 2015
Voting +1 * Verified signatures and hashes. Passed * Verified tags manually. Passed * Ability to install/uninstall Cordova. Passed * Ability to update Cordova. Passed * Ability to create blank app for Windows, WP8, Android. Passed * Ability to run apps. Passed * Reviewed release notes (Passed): plugman: CB-8416 added plugman createpackagejson . command to generate a package.json file from plugin.xml CB-8370 Update documentation for plugman publish without args cordova-lib CB-8472 Can't find config.xml error installing browser platform after plugin. (close #167) CB-8239 Fix cordova platform add PATH when PATH is relative and CWD != project root CB-8227 CB8237 CB-8238 Add --save flag and autosave to 'cordova platform add', 'cordova platform remove' and 'cordova platform update' CB-8239 Fix platform update should ignore cdv:engine (close #159) CB-8416: added plugman createpackagejson . command to create a package.json from plugin.xml CB-6973 add spec-plugman to npm run jshint CB-6973 fix spec-plugman jshint failures CB-8377 Fixed tag parsing (close #156) CB-8370 Make plugman publish without args default to CWD CB-8366 android: Remove empty `framework` directory upon uninstall CB-6973 Enable JSHint for spec-cordova CB-8239 Add support for git urls to 'cordova platform add' (close #148) CB-8358 Add `--link` for `platform add` and `platform update` CB-6973 remove base rules from individual files in src. CB-6973 have base rules in .jshintrc file. CB-8168 --list support for cordova-lib (close #145.) Chnage plugman test plugins to have IDs as directory names Make all test plugin IDs unique Empty out contents of plugin test files (and delete some unused ones) CB-8285 Don't create .fetch.json files within plugin directories CB-8286 Never persist value of create --link-to within .cordova/config.json CB-8153 generate cordova_plugins.json for browserify based projects CB-8244 android: Have `plugin add --link` create symlinks for `source-file`, `framework`, etc. CB-8226 'cordova platform add' : Look up version in config.xml if no version specified Delete root .npmignore, since there's no node module there cordova-js CB-8302 Added npm test script CB-8300 Added CI configuration files cordova-cli docs update for plugin --save CB-8439 Fix 'cordova platform update' documentation to include `plat-spec` (close #208) CB-8379 Have --version print out cordova-lib version if it's not the same as CLI's version CB-8211, CB-8358 Update `--link` help text CB-8168 --list support for CLI (close #205) CB-8227 CB-8237 CB-8238 Add --save option to 'cordova platform add', 'cordova platform remove' and 'cordova platform update' CB-5316 Spell Cordova as a brand unless it's a command or script CB-7739 document installing specific version of platforms On 3/2/15, 8:02 AM, Steven Gill stevengil...@gmail.com wrote: I have defaults.json in gitignore so it doesn't get checked in. It is a mistake to have in there. Definitely would be better to write it to some temp directory outside of source. I'll see if it causes problems. Hopefully it doesn't block release and we can just fix on master. I'll report back. On Mar 2, 2015 7:51 AM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: I vote +1: * Verified tools installation on windows * Verified new blank app could be created on windows * Verified android, ios, windows and wp8 platforms could be added, built and run. Thx! Sergey -Original Message- From: Mefire O. [mailto:ommen...@microsoft.com] Sent: Saturday, February 28, 2015 8:24 AM To: dev@cordova.apache.org Subject: RE: [Vote] Tools Release February 27, 2015 Thinking about it further, I do agree these are non-blocking. Sorry for delaying the process. I vote +1. Thanks, Mefire -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Friday, February 27, 2015 9:11 PM To: dev@cordova.apache.org Subject: RE: [Vote] Tools Release February 27, 2015 Agree with Gorkem, I think these bugs are non-blocking. I don't think we should block the release for this - this only impacts certain plugins, when using the --save feature. I think it may make sense to do a patch release, if we don't want to block this release. -Original Message- From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] Sent: Friday, February 27, 2015 8:53 PM To: dev@cordova.apache.org Subject: Re: [Vote] Tools Release February 27, 2015 On 27 Feb 2015, at 22:19, Mefire O. wrote: I've spent some time testing, found two bugs and I vote -1 until we address those : - https://issues.apache.org/jira/browse/CB-8577 I do not think this is a show stopper
RE: [Vote] Tools Release February 27, 2015
Agree with Gorkem, I think these bugs are non-blocking. I don't think we should block the release for this - this only impacts certain plugins, when using the --save feature. I think it may make sense to do a patch release, if we don't want to block this release. -Original Message- From: Gorkem Ercan [mailto:gorkem.er...@gmail.com] Sent: Friday, February 27, 2015 8:53 PM To: dev@cordova.apache.org Subject: Re: [Vote] Tools Release February 27, 2015 On 27 Feb 2015, at 22:19, Mefire O. wrote: I've spent some time testing, found two bugs and I vote -1 until we address those : - https://issues.apache.org/jira/browse/CB-8577 I do not think this is a show stopper, probably not even a bug, I have not had time to change the old feature tags. Actually, it will make the migration harder if we fix it now. - https://issues.apache.org/jira/browse/CB-8578 No idea about this one. I am still trying to figure out why this feature even exists. I should be able to send pull requests to fix them shortly. Thanks, Mefire -Original Message- From: Mefire O. [mailto:ommen...@microsoft.com] Sent: Friday, February 27, 2015 3:53 PM To: dev@cordova.apache.org Subject: RE: [Vote] Tools Release February 27, 2015 Steven, Thanks for initiating this. I'll be performing some tests/checks and will then cast my vote accordingly. Thanks, Mefire -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Friday, February 27, 2015 1:21 PM To: dev@cordova.apache.org Subject: [Vote] Tools Release February 27, 2015 Please review and vote on this Tools Release. Release issue: https://issues.apache.org/jira/browse/CB-8555 All the tools have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8555/ All the tools have also been published to npm under the rc tag. Feel free to test them with npm install -g cordova@rc The packages were published from their corresponding git tags: cordova-js: 3.8.0 (5934b1b744) cordova-lib: 4.3.0 (c4fbb6a3e1) cordova-plugman: 0.23.0 (6ec4d1d006) cordova-cli: 4.3.0 (f0fed4ad5c) Upon a successful vote I will upload the archives to dist/, publish them to NPM, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting .md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ran npm test and built a hello world android cordova project with device plugin - 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 - 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: [REVIEW] Blog post for cordova-windows 3.8.0 release
Looks good to me. On 2/27/15, 8:00 AM, Shazron shaz...@gmail.com wrote: Added you to the repo as a committer, for next time. On Fri, Feb 27, 2015 at 3:44 AM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Sent the following PR since I don't have write access to the repo. Please review and merge, all required changes and improvements are welcome. https://github.com/cordova/apache-blog-posts/pull/32/files Thx! Sergey - 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: [Discuss] Tools Release
Sergey is working on a blog post, should be out for comments later today. -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Wednesday, February 25, 2015 12:10 PM To: dev@cordova.apache.org Subject: [Discuss] Tools Release Newly Pinned: Android 3.7.1 ios 3.8.0 windows 3.8.0 Pre-req: iOS and Windows need to be published to npm. Before voting finishes, iOS and Windows need to publish their release blog posts. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE] 3.8.0 iOS Release
Voting +1 Verified archives via `coho verify-archive`. Pass € Verified tags manually. Pass € Verified blank app creates correctly with platform. Pass € Verified blank app can be successfully run and built. Pass € Checked whitespace issues. Pass € Checked Unicode issues. Pass € Ran smoke testing of mobilespec app (ran autotests). Pass € Verified compatibility with core plugins. Pass € Verified Release Notes. Pass On 2/24/15, 11:19 PM, Jesse purplecabb...@gmail.com wrote: Take off you hoser! On Feb 24, 2015, at 5:14 PM, Michal Mocny mmo...@chromium.org wrote: Jesse did it only because you said Eh nicely. On Tue, Feb 24, 2015 at 7:17 PM, Jesse purplecabb...@gmail.com wrote: +1 Ran coho check-license Verified tags Ran npm tests against tagged repo Installed plugin test framework, device plugin + tests and all tests passed on emulator cordova create ~/VoteIOS380 cd ~/VoteIOS380 cordova platform add /Repos/cordova/cordova-ios/ cordova plugin add /Repos/cordova/cordova-plugin-test-framework cordova plugin add /Repos/cordova/cordova-plugin-device cordova plugin add /Repos/cordova/cordova-plugin-device/tests ... @purplecabbage risingj.com On Tue, Feb 24, 2015 at 3:33 PM, Shazron shaz...@gmail.com wrote: Bump. This vote thread needs one more vote eh On Sun, Feb 22, 2015 at 6:30 PM, Steven Gill stevengil...@gmail.com wrote: +1 Ran coho verify-archive Created and ran cordova hello world project On Thu, Feb 19, 2015 at 3:52 PM, Shazron shaz...@gmail.com wrote: Please review and vote on this 3.8.0 iOS Release. Release issue: https://issues.apache.org/jira/browse/CB-8511 Repos ready to be released have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-8511 The package was published from its corresponding git tag: cordova-ios: 3.8.0 (d4d0c382b6) Upon a successful vote I will upload the archive to dist/, publish it to NPM, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.m d Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses - 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 - 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: [Vote] 3.8.0 Windows Release
Voting +1 € Verified archives via `coho verify-archive`. Pass € Verified tags manually. Pass € Verified blank app creates correctly with platform. Pass € Verified blank app can be successfully run and built. Pass € Checked whitespace issues. Pass € Checked Unicode issues. Pass € Ran smoke testing of mobilespec app (ran autotests). Pass € Verified compatibility with core plugins. Pass € Verified Release Notes. Pass CB-8515 Support DefaultLanguage selection for Windows CB-8321 Add supported orientations config.xml preference handling for `windows` platform CB-8525 Fix audit-license-headers check on Windows CB-8417 moved platform specific js into platform CB-8330 Added new unit tests CB-8136 Implemented prototype for end to end and unit tests via Jasmine On 2/23/15, 3:06 AM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Please review and vote on this 3.8.0 Windows Release. Release issue: https://issues.apache.org/jira/browse/CB-8524 Repos ready to be released have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-8524 The package was published from its corresponding git tag: cordova-windows: 3.8.0 (d13e7ff25f) Upon a successful vote I will upload the archive to dist/, publish it to NPM, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. I vote +1: * Ran coho audit-license-headers * Manually verified platform could be added, built and run Thx! -Sergey - 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: Plugin history purged from registry?
Should we put out a blog post, telling that plugin authors may need to republish old version? Could also be a way to refer to our move to npm :) -Original Message- From: Chuck Lantz [mailto:cla...@microsoft.com] Sent: Monday, February 16, 2015 1:37 PM To: dev@cordova.apache.org; Nick Martin Subject: RE: Plugin history purged from registry? Thanks Steve - We verified all of the pinned plugins in VS are working again! -Chuck -Original Message- From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Monday, February 16, 2015 1:24 PM To: Nick Martin Cc: dev@cordova.apache.org Subject: Re: Plugin history purged from registry? Okay they are all up again. I had to change the latest tag for all of them back to what it should be. Ownership is messed up right now. Only Andrew and myself are listed as owners for the plugins. I will have to readd all of you who want the ability to publish core plugins. Let me know if you do. I am going to look into blocking plugman 0.22.17 again. Don't want the bug from January to pop back up. Plugin authors will have to republish old versions of their plugins if they have lost their history. On Mon, Feb 16, 2015 at 1:11 PM, Nick Martin n...@meteor.com wrote: Thank you, Steve! -- Nick On Mon, Feb 16, 2015 at 11:35 AM, Chuck Lantz cla...@microsoft.com wrote: Awesome! Do let us know if you need help. Nikhil was digging in a bit but we'll hold given this update. -Chuck From: Steven Gill [mailto:stevengil...@gmail.com] Sent: Monday, February 16, 2015 11:29 AM To: Chuck Lantz Cc: dev@cordova.apache.org Subject: Re: Plugin history purged from registry? It looks like the problem lies with the check I added to prevent plugman 0.22.17 from publishing. I have removed that check and updated the DB. In the process of uploading old core plugins now. I will figure out a better check after all of the plugins have been uploaded again. On Sun, Feb 15, 2015 at 8:17 PM, Chuck Lantz cla...@microsoft.com mailto:cla...@microsoft.com wrote: Yeah Visual Studio is in a similar boat for projects where devs have not used a plugin before. (We fortunately switched to storing the plugins in the project in our latest update so existing projects work.) We're directing people to use git URIs near term when acquiring plugins. Steve, let us know if you need assistance. I can chat with folks about pitching in if it would be helpful. (But know too many cooks can be a problem too.) From: Nick Martin n...@meteor.commailto:n...@meteor.com Sent: Sunday, February 15, 2015 6:50 PM To: Steven Gill Cc: dev@cordova.apache.orgmailto:dev@cordova.apache.org Subject: Re: Plugin history purged from registry? Hi Steven, Thank you for your work on this issue. I know it's the weekend, and I appreciate you going above and beyond. Do you have any idea if and when old versions of plugins will be restored to the site? This issue is biting our users pretty hard -- we pin plugins to stable versions so users are not taken by surprise when new versions come out. Old versions being missing means none of our users can re-build or update their apps! Even a rough order of magnitude estimate would be helpful. We have to decide if we need to push out an emergency patch release on Monday to upgrade to the latest versions still in the registry. Thanks again, -- Nick - 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
[DISCUSS] Cordova-Windows@3.7.2 release
Hi, It has been a while since we did a Windows release. I specifically wanted to start a discuss thread to release Windows due to the following issue that had been fixed, but looks like was never released out. The bug (https://issues.apache.org/jira/browse/CB-7985) is about not being able to build Windows on Visual Studio 14 CTP tools. This fix (https://github.com/apache/cordova-windows/commit/84c9547ab58bb256a3054f29612daec3d41196bc) is pretty simple. With more people now starting to have VS 2014, I think we should make this release. Are there any other parts that should go in this release?
Re: [Review] Plugins Package.json
+1 to changing cordova-windows8 to cordova-windows.
On 2/4/15, 12:05 PM, Jesse purplecabb...@gmail.com wrote:
Yes, you can skip all the 'windows8' stuff and just use 'windows'.
windows8 is legacy and slowly all plugins are being migrated to just use
the 'windows' section in plugin.xml
@purplecabbage
risingj.com
On Wed, Feb 4, 2015 at 11:36 AM, Steven Gill stevengil...@gmail.com
wrote:
I have made the changes you suggested. I like the idea of cordova parent
key.
I added cordova-windows8 as a keyword but I would like someone from
microsoft to chime in about it. My understanding is that windows8 is
around
for legacy and windows is preferred. Please correct me if I'm wrong. I'd
prefer to just list windows and cordova-windows.
If anyone else has feedback on the package.json file, please share! You
can
view it at
https://github.com/stevengill/cordova-plugin-device/blob/npmpub/package.j
son
I am working on createpackagejson command now
https://issues.apache.org/jira/browse/CB-8416
On Tue, Feb 3, 2015 at 5:29 PM, Andrew Grieve agri...@chromium.org
wrote:
From looking at it, only thought is whether we should put all of the
non-standard fields into a cordova parent key. E.g.:
{
name: cordova-plugin-device,
cordova: {
id: org.apache.cordova.device,
platforms: [...]
}
}
Sounds like we need to re-write the file when publishing to CPR
anyways,
so
transforming from this to what is currently expected can be done in
that
step.
Other tidbits:
- windows8 is missing from keywords. Intentional? (not sure if
windows is
now an alias?)
- author: might just set this to Apache
On Tue, Feb 3, 2015 at 7:50 PM, Steven Gill stevengil...@gmail.com
wrote:
Please review at
https://github.com/stevengill/cordova-plugin-device/blob/npmpub/package.j
son
You will notice that I added cordova-PLATFORM as a keyword.
I have also kept the platforms tag for now. I can remove it but
maybe
we
can find some future use for it. We currently need it when
publising to
CPR
but can add/rm it during plugman publish.
I am going to create a createpackagejson command in plugman that
will
build
something like this from plugin.xml. Other plugin devs will be able
to
use
this command to quickly add package.json files to their plugins.
I will then modify plugman publish to use the createpackagejson
command
if
needed. Plugman publish will still have to add the contents of the
readme
(or doc/index.md) to the package.json as well as the platforms tag
if
we
decide to remove it. It will also have to change the package-name
field
to
package-id when publishing to CPR. Once published, we can remove
these
changes package.json.
If the package.json file looks good, I'm going to start adding one
to
all
of our plugins.
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Monthly Hangouts - Jan 2015 Edition
I have closed the poll for the dates on Doodle. Based on the responses, we should schedule the hangout for - Thu Jan 29 2015 - 1:00 PM EST Please mark your calendars, and looking forward to a great discussion :) The hangout could spill to more than 1 hour, and 2:00PM EST also looks good for a lot of people. Can someone create the hangout link closer to the date? -Original Message- From: Parashuram N (MS OPEN TECH) [mailto:panar...@microsoft.com] Sent: Sunday, January 25, 2015 7:55 PM To: dev@cordova.apache.org Subject: Re: Monthly Hangouts - Jan 2015 Edition Planning to close this poll for the doodle. The times that seem to work for most people now are (2 conflicts max) - Wednesday 28 Jan, 12:00pm EST - Thu 29 Jan 1pm EST - Thu 29 Jan 2pm EST I will close the poll tomorrow at 9AM PST so that the hangouts can be scheduled. On 1/23/15, 7:07 AM, Michal Mocny mmo...@chromium.org wrote: Thanks Parashuram for coordinating. On Thu, Jan 22, 2015 at 8:04 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Wanted to bump up the thread about the Cordova hangouts. A lot of people have responded, and looks like the following times are candidates. - Monday 26 Jan 2015, 1:00pm EST (1 conflict) - Thu 29 Jan 2015 2:00 PM EST (1 conflict) We could finalize this tomorrow, and if you have not already added yourself to the doodle, please do at - http://doodle.com/a3kr2kek4a5spxpr. -Original Message- Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition Here is the Doodle - http://doodle.com/a3kr2kek4a5spxpr. Please mark your availability. I added this for the next week, guessing that it would be super hard to finalize this week. If next week does not work, we could make do this in Feb. - ADMIN STUFF P.S: If anyone wants to administer the poll to change the time, or add additional days, here is the admin link. http://doodle.com/a3kr2kek4a5spxpr6c9pf857/admin#admin. DO NOT use this link for scheduling, only use it to make changes or administer the doodle. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition There's no account. (don't think doodle requires sign-up) On Tue, Jan 20, 2015 at 3:33 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Hi, It has been a while since we had a hangouts, and a lot of folks have suggested that there are topics that could use a hangout. Thanks Michael for creating the agenda doc. https://docs.google.com/document/d/1h4KKT0oc70BE57eJ7Bmn4c-at7dH20g0KxTKv lyvIZU/edit?usp=sharing Do we have an official account where we set up the doodle? If not, I could set up a doodle for this. - 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 - 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: Monthly Hangouts - Jan 2015 Edition
Planning to close this poll for the doodle. The times that seem to work for most people now are (2 conflicts max) - Wednesday 28 Jan, 12:00pm EST - Thu 29 Jan 1pm EST - Thu 29 Jan 2pm EST I will close the poll tomorrow at 9AM PST so that the hangouts can be scheduled. On 1/23/15, 7:07 AM, Michal Mocny mmo...@chromium.org wrote: Thanks Parashuram for coordinating. On Thu, Jan 22, 2015 at 8:04 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Wanted to bump up the thread about the Cordova hangouts. A lot of people have responded, and looks like the following times are candidates. - Monday 26 Jan 2015, 1:00pm EST (1 conflict) - Thu 29 Jan 2015 2:00 PM EST (1 conflict) We could finalize this tomorrow, and if you have not already added yourself to the doodle, please do at - http://doodle.com/a3kr2kek4a5spxpr. -Original Message- Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition Here is the Doodle - http://doodle.com/a3kr2kek4a5spxpr. Please mark your availability. I added this for the next week, guessing that it would be super hard to finalize this week. If next week does not work, we could make do this in Feb. - ADMIN STUFF P.S: If anyone wants to administer the poll to change the time, or add additional days, here is the admin link. http://doodle.com/a3kr2kek4a5spxpr6c9pf857/admin#admin. DO NOT use this link for scheduling, only use it to make changes or administer the doodle. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition There's no account. (don't think doodle requires sign-up) On Tue, Jan 20, 2015 at 3:33 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Hi, It has been a while since we had a hangouts, and a lot of folks have suggested that there are topics that could use a hangout. Thanks Michael for creating the agenda doc. https://docs.google.com/document/d/1h4KKT0oc70BE57eJ7Bmn4c-at7dH20g0KxTKv lyvIZU/edit?usp=sharing Do we have an official account where we set up the doodle? If not, I could set up a doodle for this. - 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 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [VOTE] 3.7.0 Android Platform release
I vote +1 • Verified tags • Ran smoke testing of mobilespec app (autotests) and compatibility with core plugins. -Original Message- From: Sergey Grebnov (Akvelon) [mailto:v-seg...@microsoft.com] Sent: Thursday, January 22, 2015 10:51 AM To: dev@cordova.apache.org Subject: RE: [VOTE] 3.7.0 Android Platform release I vote +1 • Verified archives via `coho verify-archive`. • Verified tags manually. • Verified blank app can be created and run • Ran smoke testing of mobilespec app (autotests) and compatibility with core plugins. • Verified Release Notes. Thx! Sergey -Original Message- From: Joe Bowser [mailto:bows...@gmail.com] Sent: Wednesday, January 21, 2015 8:10 PM To: dev Subject: [VOTE] 3.7.0 Android Platform release Please review and vote on this 3.7.0 Android Platform Release. Release issue: https://issues.apache.org/jira/browse/CB-8335 Repos ready to be released have been published to dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8335/ The packages were published from their corresponding git tags: cordova-android: 3.7.0 (f3885692d9) Upon a successful vote I will upload the archives to dist/, publish them to NPM, and post the corresponding blog post. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 72 hours. I vote +1: * Ran coho audit-license-headers over the relevant repos * Ran coho check-license to ensure all dependencies and subdependencies have Apache-compatible licenses * Ran hello world Note: This is the first time we've done an independent platform release, and as much as I'd like this thing to go out, it'd be good to smooth-out this release process while we're here. I've added my signing key to cordova-dist for verification. Please keep adding feedback on this in the discuss thread. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: Monthly Hangouts - Jan 2015 Edition
Wanted to bump up the thread about the Cordova hangouts. A lot of people have responded, and looks like the following times are candidates. - Monday 26 Jan 2015, 1:00pm EST (1 conflict) - Thu 29 Jan 2015 2:00 PM EST (1 conflict) We could finalize this tomorrow, and if you have not already added yourself to the doodle, please do at - http://doodle.com/a3kr2kek4a5spxpr. -Original Message- Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition Here is the Doodle - http://doodle.com/a3kr2kek4a5spxpr. Please mark your availability. I added this for the next week, guessing that it would be super hard to finalize this week. If next week does not work, we could make do this in Feb. - ADMIN STUFF P.S: If anyone wants to administer the poll to change the time, or add additional days, here is the admin link. http://doodle.com/a3kr2kek4a5spxpr6c9pf857/admin#admin. DO NOT use this link for scheduling, only use it to make changes or administer the doodle. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition There's no account. (don't think doodle requires sign-up) On Tue, Jan 20, 2015 at 3:33 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Hi, It has been a while since we had a hangouts, and a lot of folks have suggested that there are topics that could use a hangout. Thanks Michael for creating the agenda doc. https://docs.google.com/document/d/1h4KKT0oc70BE57eJ7Bmn4c-at7dH20g0KxTKvlyvIZU/edit?usp=sharing Do we have an official account where we set up the doodle? If not, I could set up a doodle for this. - 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: Monthly Hangouts - Jan 2015 Edition
Here is the Doodle - http://doodle.com/a3kr2kek4a5spxpr. Please mark your availability. I added this for the next week, guessing that it would be super hard to finalize this week. If next week does not work, we could make do this in Feb. - ADMIN STUFF P.S: If anyone wants to administer the poll to change the time, or add additional days, here is the admin link. http://doodle.com/a3kr2kek4a5spxpr6c9pf857/admin#admin. DO NOT use this link for scheduling, only use it to make changes or administer the doodle. -Original Message- From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve Sent: Tuesday, January 20, 2015 1:07 PM To: dev Subject: Re: Monthly Hangouts - Jan 2015 Edition There's no account. (don't think doodle requires sign-up) On Tue, Jan 20, 2015 at 3:33 PM, Parashuram N (MS OPEN TECH) panar...@microsoft.com wrote: Hi, It has been a while since we had a hangouts, and a lot of folks have suggested that there are topics that could use a hangout. Thanks Michael for creating the agenda doc. https://docs.google.com/document/d/1h4KKT0oc70BE57eJ7Bmn4c-at7dH20g0KxTKvlyvIZU/edit?usp=sharing Do we have an official account where we set up the doodle? If not, I could set up a doodle for this. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Monthly Hangouts - Jan 2015 Edition
Hi, It has been a while since we had a hangouts, and a lot of folks have suggested that there are topics that could use a hangout. Thanks Michael for creating the agenda doc. https://docs.google.com/document/d/1h4KKT0oc70BE57eJ7Bmn4c-at7dH20g0KxTKvlyvIZU/edit?usp=sharing Do we have an official account where we set up the doodle? If not, I could set up a doodle for this.
Re: CI for cordova-js and cordova-cli
I also voted +1 on this. Interesting that this needs a +1 vote - don¹t we already have travis and appveyor enabled for a few of the repos? On 1/16/15, 3:10 PM, Jesse purplecabb...@gmail.com wrote: The issue I created for infra is here: INFRA-9017 [1] Unfortunately they are claiming to not support AppVeyor, and saying they don't do anything special for TravisCI. Please vote up this issue. Cheers, Jesse [1] https://issues.apache.org/jira/browse/INFRA-9017 @purplecabbage risingj.com On Fri, Jan 16, 2015 at 10:53 AM, Jesse purplecabb...@gmail.com wrote: Underway for Cordova-js. I created an issue with infra to setup the integration. Issue# to follow once I am at a computer. On Jan 16, 2015, at 9:04 AM, Alexander Sorokin alexander.soro...@akvelon.com wrote: Hi Guys, I like the cordova-lib CI via Travis and AppVeyor. I would like to add this feature to cordova-js and cordova-cli. I've proposed Travis and AppVeyor scripts to these repositories. Now they are merged into master. I assume the next step is to wire Travis and AppVeyor to repositories. What do you think about it? And who can do it? Regards, Alexander Sorokin - 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: https://www.apache.org/dist/cordova/
I think this is the official distribution. Not sure if Apache recognized npm as the official distribution and may be does not guarantee the integrity of the package on npm ? -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Monday, January 12, 2015 11:45 AM To: dev@cordova.apache.org Subject: Re: https://www.apache.org/dist/cordova/ Steven Gill wrote: Installing through dist isn't our recommended way to install Cordova. If rather have people have to read the blog than just press a big download button without reading. Are we required by apache to have this thing? Because, I'd rather have something that says run `npm install cordova` than the rather notable download thing that takes me to a useless / confusing section — this is from the main http://cordova.apache.org/ page: DOWNLOAD Cordova version 4.0.0 http://cordova.apache.org/#download Clicking the download button-link-thing takes you to: Download Archives It is recommended that the cordova CLI be installed from npm rather than downloading this .zip version. ^ note that there is no explanation here about how to use npm to install cordova (or how to get npm) For more information on installing the npm version see the Command-Line Interface http://cordova.apache.org/docs/en/4.0.0//guide_cli_index.md.html#The%20Com mand-Line%20Interface section of the documentation. ^ well, there's this, but it's TL;DR You can find our release zips with corresponding OpenPGPkeys, MD5 and SHA files on the Apache Cordova dist page https://www.apache.org/dist/cordova/. Our artwork http://cordova.apache.org/artwork.html is also available. Older versions can be downloaded from the archive http://archive.apache.org/dist/cordova/. This entire section is really poorly organized. :(
Re: platforms/plugins save and restore from config.xml
Regarding save - I think automatic save could be an issue for folks who want to try out experimental platforms, or pick up platforms from git URIs or master branches. What would happen in that case? May be that's is why npm --save exists in the first place. Where to save - For making progress, looks like we will also have to finalize if it will be persisted in config.xml or in package.json. Most IDEs will not use the --save option, but may choose to directly persist in the required file when a platform is added using a GUI. Regarding restore - automatic restore makes a lot of sense. Does mefire's PR not cover that ? From: Chuck Lantzmailto:cla...@microsoft.com Sent: ?Friday?, ?January? ?9?, ?2015 ?12?:?43? ?PM To: dev@cordova.apache.orgmailto:dev@cordova.apache.org Cc: Michael Brooksmailto:mbro...@adobe.com +1 on automating. That's why Mefire's PR for platform add just uses the version information in config.xml if it is present. I think the idea behind --save was to make this npm-like so that if a value is already in config.xml, then you can also update it by specifying a different version and saving it. (Similar to how npm install cordova@4.1.2 --save would update package.json in the directory you're executing the command even if an earlier version was present). He mentioned the two PRs on the --save for platform earlier in the this thread. As an improvement it could just save by default if there is nothing present in config.xml. Personally I'd always use --save. I also agree what we do for platforms we should likely do for plugins too. Now, we had originally said in a hangout that config.xml should contain app stuff and that platform and plugin versions and preferences/params qualified as app stuff. We could certainly go towards package.json (or something package.json-like) since that's really what we're trying to emulate here at the end of the day I think. However, I also thought we said that config.xml was too engrained to move away from it (though clearly the web as a whole is moving towards the W3C app manifest). If we don't use config.xml, it definitely needs to be a document at the root level not under .cordova since you should clearly check it into source control and it shouldn't be hidden. It's details about the app not how the CLI should behave. -Chuck -Original Message- From: Josh Soref [mailto:jso...@blackberry.com] Sent: Friday, January 9, 2015 11:26 AM To: dev@cordova.apache.org Cc: Michael Brooks Subject: Re: platforms/plugins save and restore from config.xml Leo wrote: I had asked some questions about save and restore a while back One of my biggest questions was why would these commands be an option? I can't think of any reasons. What I'm looking for, as soon as possible, is that Cordova 'project' metadata is stored logically and consistently so that the CLI and multiple IDEs could simultaneously work on the same project and know about what each other have done wrt. adding/removing plugins/platforms/etc. Seems reasonable Does removing experimental advance that goal or does it, as Michal says, put obstacles in the path of getting there by requiring long term support of an incomplete and possibly confusing (more options?) solution? I think Michal is right. It probably makes more sense to integrate the code behind save/restore into (platform|plugin) add and (something) so that it automatically just works. I'm not sure offhand what 'restore' would look like in a such a model though... Also worth considering is the recent request for `cordova run not-installed-platform` `cordova run not-installed-platform` (CB-8283) should honor the values from `cordova platform save` That might be the replacement for 'restore', although it probably isn't ideal...
Re: platforms/plugins save and restore from config.xml
+1 to graduating this out of experimental :) On 1/8/15, 4:25 PM, Steven Gill stevengil...@gmail.com wrote: +1 to remove --experimental On Thu, Jan 8, 2015 at 4:13 PM, Gorkem Ercan gorkem.er...@gmail.com wrote: On 8 Jan 2015, at 17:29, Mefire O. wrote: Hi all, I am a big fan of the experimental save and restore features that are in the CLI and saw that Gorkem has also created another PR ( https://github.com/apache/cordova-lib/pull/143 ) to have a setting to auto persist/restore plugin versions which is a really interesting idea. Glad it helps someone. The current PR is for plugins and I will send a PR for platforms too. The ultimate goal is to be able to remove platforms and plugins folder completely. On a related note, one issue I ran into with platform save/restore is when you need to involve multiple operating systems for a given project. Ex: Targeting say iOS, Windows, and Ubuntu from the same project or simply have some team members on OSX or Linux while others are on Windows - you need to be able to save or restore only platforms that run on the OS you are currently using. For the restore situation, it seems to make quite a bit of sense to use any version information in config.xml when you add a platform by default. The fact the information in is in config.xml indicates the goal is consistency. Here is a PR that adds this functionality for platforms: https://github.com/apache/cordova-lib/pull/140#issuecomment-68942932 This functionality makes a lot of sense especially if/when it supports git urls? With that in mind, we could also follow that familiar pattern that exists with npm and package.json to help out when you want to quickly save the platform you added to config.xml. Ex: cordova platform add android --save I think we should have support for --save on plugins add/remove as well. Ultimately, I think users of this functionality configure their projects to be auto restore and use this or the save/restore commands to specify what needs to be restored. There is one catch with the implementation though. Save and restore are still called with --experimental, perhaps we need to remove --experimental before this can proceed. ...adds the latest android platform and updates config.xml with the version that was added. As always, you can always use the existing syntax to add a different version (cordova platform add android@4.0.0mailto: android@4.0.0). I'm planning on putting together a PR on that idea as well. We could actually follow a similar model for plugins as well. Thanks, Mefire - 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: Automated Unit-Testing for my plugin?
It would be awesome if we could get medic to run plugins tests on custom plugins also, and if plugin developers could use this. What do you guys think? On 12/31/14, 5:07 AM, Michael Bishop mbis...@fiksu.com wrote: Thank you very much! _ michael On Tue, Dec 30, 2014 at 4:35 PM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Michael, take a look on the cordova-mobile-spec[1] which utilizes 'cordova-plugin-test-framework', there is special setting[2] here to specify what plugins to test. * You can use your custom Jasmine reporter which will trace tests results to the console (see example [4]) I also recommend to take a look on Apache Cordova Medic[3] which is an automated test system built on top of cordova-mobile-spec; PS. we are working on some improvements to allow adding non-core plugins for testing [1]https://github.com/apache/cordova-mobile-spec [2] https://github.com/apache/cordova-mobile-spec/blob/master/dependencies-pl ugin/plugin.xml [3] https://github.com/apache/cordova-medic [4] http://jasmine.github.io/2.1/custom_reporter.html Thx! Sergey -Original Message- From: Michael Bishop [mailto:mbis...@fiksu.com] Sent: Tuesday, December 30, 2014 8:18 PM To: dev@cordova.apache.org Subject: Automated Unit-Testing for my plugin? Hello Cordova Folk! I have written small plugin for Cordova but want to automate my unit tests. I'm wondering what the endorsed solution is. Here's what I have: - Plugin - 'tests' directory (and associated plugin.xml file) - I've successfully used the 'cordova-plugin-test-framework' in a sample app where I've also included my plugin and the plugin's test plugin. The tests are running just fine. My question(s): How would I automate my test suite? Is it possible to run it via a command-line tool and retrieve the results? Many thanks as I know you are still developing this stuff! _ michael - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Tools Release
+1 to removing that specific commit and continuing with the release process. I have also forked this thread where we should continue the discussion (so as not to overload the DISCUSS thread). On 1/5/15, 6:43 PM, Andrew Grieve agri...@chromium.org wrote: Josh - thanks for pointing out that the change isn't working as intended. I did some testing before merging, but didn't try the error conditions. I've just reverted the one to CLI that enables the flag. Let's move forward with releasing :) Also noticed that if you have an older-than-master version of android installed in your project, then you get: $ cordova run --list Running command: /Users/agrieve/git/cordova/cordova-cli/foo/platforms/android/cordova/run --list ERROR : Run option '--list' not recognized. ERROR running one or more of the platforms: Error: /Users/agrieve/git/cordova/cordova-cli/foo/platforms/android/cordova/run: Command failed with exit code 2 You may not have the required environment or OS to run this project I actually do like the syntax of cordova run --list, since the run command is the thing that --target is relevant to anyways. Maybe --list-targets would be more explicit? Adding cordova target add would be overstepping I think. You can add Android emulator targets as well, but us writing a wrapper for the logic would just make things more complicated I think. I do think that having cordova-lib look for the existence of the list-emulator-images and list-devices scripts makes sense, and just have it call them directly. On Mon, Jan 5, 2015 at 5:29 PM, Josh Soref jso...@blackberry.com wrote: Murat Sutunc wrote: 1) When provided with an unknown extra parameter, such as --list in this case, all the platforms ignore it. This looks like the expected behavior as there are several issues in Jira related to it. (ex. See bug CB-6676 - https://issues.apache.org/jira/browse/CB-6676?jql=project%20%3D%20CB%20AN D %20text%20~%20%22ignore%20parameter%22). Exit code 1 on Blackberry seems like a bug. https://wiki.apache.org/cordova/CommandLineToolingDesign#Errors * 1: not implemented / unsupported command I believe that what windows phone was doing was correct. And if someone is changing the contract, they failed to update the contract. 2) Introducing 'target' as a top level option seems like a new proposal. My thoughts were to avoid having a new top level command for listing devices but I would like to hear others opinions on this as well. I also think 'target' might not be the best choice of keyword here as it's already part of 'run' and it's easy to get confused: cordova run --target=FOO cordova target --list Not --list, just plain list. As in cordova platform list, and cordova plugin list, it's a commonly used idiom in cordova. 3) I don¹t understand the 'cordova target add' command completely. Is it an alias to 'cordova platform add'? No. For blackberry10 you can configure a target which is a name for a set of settings (including an ip address/dns name, whether it is a device/simulator, and a device password). You can then use run --target=foo. 4) 'Each platform should already support the list-* commands' is currently not true. firefoxos, browser, Ubuntu don¹t support it. Those platforms aren't complete, it's part of the contract, but we already have a good way of handling missing components of lib/ ‹ if they don't exist (we can check for this), or aren't implemented (they return a standard value). The way you've implemented it with run, there's no way to look before you leap, which results in the failure that you introduced for blackberry10. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Cordova --list option implementation
Forking from Re: [DISCUSS] Tools Release to continue discussion. +1 to Andrew suggestion that adding a top level command just for listing targets would be an overkill. Also, people usually want to see the supported targets when they run, so it makes sense to expose it closer to where it gets used. If we decide that cordova target add could be used to create new targets, that could be a separate top level command, can `cordova run ‹list` could be the alias for `cordova target platform list` command (though I am not a fan of aliasing commands). Josh, is your concern that ‹list throws an error in case of blackberry? We could fix that by either 1a- Ignoring unknown flags like other platforms - and document the ignoring part as the default behavior 1b - or change other platforms to throw error on unsupported flags. In this case, ‹list would do the check to see if ‹list is implemented first. 2. Implement ‹list for blackberry, thereby not having error on any platform. We could then have a separate discussion about what happens when a flag is not supported by a platform. It would be great if we can let users use the ‹list functionality with minimal disruption to any platform. On 1/5/15, 6:43 PM, Andrew Grieve agri...@chromium.org wrote: Josh - thanks for pointing out that the change isn't working as intended. I did some testing before merging, but didn't try the error conditions. I've just reverted the one to CLI that enables the flag. Let's move forward with releasing :) Also noticed that if you have an older-than-master version of android installed in your project, then you get: $ cordova run --list Running command: /Users/agrieve/git/cordova/cordova-cli/foo/platforms/android/cordova/run --list ERROR : Run option '--list' not recognized. ERROR running one or more of the platforms: Error: /Users/agrieve/git/cordova/cordova-cli/foo/platforms/android/cordova/run: Command failed with exit code 2 You may not have the required environment or OS to run this project I actually do like the syntax of cordova run --list, since the run command is the thing that --target is relevant to anyways. Maybe --list-targets would be more explicit? Adding cordova target add would be overstepping I think. You can add Android emulator targets as well, but us writing a wrapper for the logic would just make things more complicated I think. I do think that having cordova-lib look for the existence of the list-emulator-images and list-devices scripts makes sense, and just have it call them directly. On Mon, Jan 5, 2015 at 5:29 PM, Josh Soref jso...@blackberry.com wrote: Murat Sutunc wrote: 1) When provided with an unknown extra parameter, such as --list in this case, all the platforms ignore it. This looks like the expected behavior as there are several issues in Jira related to it. (ex. See bug CB-6676 - https://issues.apache.org/jira/browse/CB-6676?jql=project%20%3D%20CB%20AN D %20text%20~%20%22ignore%20parameter%22). Exit code 1 on Blackberry seems like a bug. https://wiki.apache.org/cordova/CommandLineToolingDesign#Errors * 1: not implemented / unsupported command I believe that what windows phone was doing was correct. And if someone is changing the contract, they failed to update the contract. 2) Introducing 'target' as a top level option seems like a new proposal. My thoughts were to avoid having a new top level command for listing devices but I would like to hear others opinions on this as well. I also think 'target' might not be the best choice of keyword here as it's already part of 'run' and it's easy to get confused: cordova run --target=FOO cordova target --list Not --list, just plain list. As in cordova platform list, and cordova plugin list, it's a commonly used idiom in cordova. 3) I don¹t understand the 'cordova target add' command completely. Is it an alias to 'cordova platform add'? No. For blackberry10 you can configure a target which is a name for a set of settings (including an ip address/dns name, whether it is a device/simulator, and a device password). You can then use run --target=foo. 4) 'Each platform should already support the list-* commands' is currently not true. firefoxos, browser, Ubuntu don¹t support it. Those platforms aren't complete, it's part of the contract, but we already have a good way of handling missing components of lib/ ‹ if they don't exist (we can check for this), or aren't implemented (they return a standard value). The way you've implemented it with run, there's no way to look before you leap, which results in the failure that you introduced for blackberry10. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
