Re: [NOTICE] Intent on moving to Github
ASF will allow it, other projects already showed interest and at ApacheCon they made it public that they will allow it to any project My incubator project OpenWhisk is the first one to work out all the kinks For now let know everyone that wants write access, specially those that are repo owners and usually in charge of merging PRs to: 1. associate your github id in id.apache.org profile 2. enable 2FA in Github.com 3. show up properly under whimsy https://whimsy.apache.org/roster/committee/cordova Once the repos are transferred, a Github team will be created cordova-committers and folks that go thru gitbox setup will be added to this team, this team will have write access to all github.com/apache/cordova* repos Once transferred need to make it clear to all committers to reconfigure their git upstream, and no longer write to git-wip other projects that moved over like traffic server, went ahead and migrated all the JIRA Issues to Github Issues, a topic for another thread :-) let me know how I can help, will be glad --Carlos On Tue, Jun 6, 2017 at 6:30 PM Steven Gill wrote: > Yay! Hope ASF allows us to finally do this! > > On Tue, Jun 6, 2017 at 3:28 PM, Filip Maj wrote: > > > My one comment is OMG YISS! > > > > On Mon, Jun 5, 2017 at 6:41 PM, Shazron wrote: > > > The Apache Cordova Project Management Committee (PMC) has consensus > that > > we > > > should move primary development of Apache Cordova to Github, from > > Apache's > > > servers (role would be reversed, Apache would then be the mirror now). > > > > > > We are already processing pull requests through Github, although > without > > > write access we couldn't label, or close PRs directly. Enabling of > Issues > > > in Github (to replace JIRA) would be a separate matter, and would > likely > > be > > > on a per-repo basis. > > > > > > Moving is achieved by invitation to the Apache Gitbox project: > > > https://gitbox.apache.org/ (don't get excited if you can log in and > > link, > > > your repo needs to be whitelisted) > > > > > > We would have to file INFRA issues in JIRA to get approval for the > move. > > > > > > We are suggesting a multi-part migration: > > > > > > 1. Top platforms (ios, android, windows, browser) > > > 2. Tools (lib, cli, coho, fetch, common etc) --> we might need a lib > > > breakout first, this is ongoing work > > > 3. All plugins > > > > > > The rest would be on a "as needed" basis. > > > > > > Comments, if any? > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
Re: browsing mailing lists?
Thanks Shaz for the link ! This is why ponymail.apache.org was not working for me :-) On Mon, Jan 9, 2017 at 1:50 PM Shazron wrote: > Yes we should change it. > > https://lists.apache.org/list.html?cordova.apache.org > > On Mon, Jan 9, 2017 at 9:50 AM, Carlos Santana > wrote: > > > I was looking on where to search an browse the mailing list, the website > > points to markmail [1], but I thought there was a new system to browse > > implemented recently > > > > anyone knows where that new system is? and if we should change the > website > > contact page? > > > > [1] http://cordova.apache.org/contact/ > > >
browsing mailing lists?
I was looking on where to search an browse the mailing list, the website points to markmail [1], but I thought there was a new system to browse implemented recently anyone knows where that new system is? and if we should change the website contact page? [1] http://cordova.apache.org/contact/
Re: [DISCUSS] Plugins Release
Ok Shaz, you have access to all cordova plugins on npm now Keep the good work adn train moving forward shoo shoo !!! On Mon, Dec 12, 2016 at 8:06 AM Carlos Santana wrote: > Shaz giving you access at the moment, should be done in 5 minutes > > On Sun, Dec 11, 2016 at 5:37 PM Shazron wrote: > >> Hi Steve Gill and/or Carlos Santana -- please give me write access to >> these >> npm modules below. Publishing is stalled until I get permissions. >> >> cordova-plugin-battery-status >> csantanapr >> stevegill >> cordova-plugin-camera >> csantanapr >> stevegill >> cordova-plugin-console >> csantanapr >> stevegill >> cordova-plugin-contacts >> csantanapr >> stevegill >> cordova-plugin-device >> csantanapr >> stevegill >> cordova-plugin-device-motion >> csantanapr >> stevegill >> cordova-plugin-device-orientation >> csantanapr >> stevegill >> cordova-plugin-dialogs >> csantanapr >> stevegill >> cordova-plugin-file >> kotikov.vladimir >> csantanapr >> stevegill >> cordova-plugin-file-transfer >> nikhilkh >> csantanapr >> stevegill >> cordova-plugin-geolocation >> csantanapr >> stevegill >> cordova-plugin-globalization >> csantanapr >> stevegill >> cordova-plugin-legacy-whitelist >> csantanapr >> stevegill >> cordova-plugin-media >> kotikov.vladimir >> csantanapr >> stevegill >> cordova-plugin-media-capture >> csantanapr >> stevegill >> cordova-plugin-network-information >> csantanapr >> stevegill >> cordova-plugin-screen-orientation >> gbenvenuti >> stevegill >> tony-- >> cordova-plugin-splashscreen >> kotikov.vladimir >> csantanapr >> stevegill >> cordova-plugin-statusbar >> kotikov.vladimir >> csantanapr >> stevegill >> cordova-plugin-test-framework >> csantanapr >> stevegill >> cordova-plugin-vibration >> csantanapr >> stevegill >> cordova-plugin-whitelist >> csantanapr >> stevegill >> >> -- >> >> I already have access to these: >> >> cordova-plugin-wkwebview-engine >> bowserj >> kotikov.vladimir >> purplecabbage >> shazron >> csantanapr >> stevegill >> cordova-plugin-inappbrowser >> csantanapr >> stevegill >> kotikov.vladimir >> sgrebnov >> shazron >> >> >> On Sun, Dec 11, 2016 at 2:11 PM, Shazron wrote: >> >> > I've already started https://issues.apache.org/jira/browse/CB-12237 >> > >> > On Sun, Dec 11, 2016 at 2:01 PM, Shazron wrote: >> > >> >> One more issue -- cordova-plugin-inappbrowser, my intent is not to call >> >> anyone out here (hey I'm the major source of mistakes for this >> release) but >> >> my intent is to fix the problem. The plugin minor version was >> incremented >> >> in plugin.xml to 1.6.0 but not incremented in package.json. Thus when >> the >> >> packaging automation ran, the version had a mismatch, and that this is >> >> reflected in cordova-plugin-inappbrowser. >> >> >> >> https://github.com/apache/cordova-plugin-inappbrowser/commit >> >> /cfbd3845a893df647ff39ec3c750804d775a0e57 >> >> >> >> We should have a version mismatch automation check during release as >> well >> >> in coho, and/or the tests. >> >> >> >> So now the problem is, I can't publish cordova-plugin-inappbrowser this >> >> release because package.json shows the version is 1.5.1 while >> plugin.xml is >> >> 1.6.0 (1.6.0 is correct). >> >> >> >> I will have to omit cordova-plugin-inappbrowser in this release, and >> put >> >> out another cordova plugins release which includes: >> >> >> >> 1) Updates in cordova-plugin-battery-status that we discussed >> >> 2) The package.json update in cordova-plugin-inappbrowser (same >> version, >> >> 1.6.0) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Sun, Dec 11, 2016 at 11:32 AM, Shazron wrote: >> >> >> >>> I screwed up the release notes fo
Re: [DISCUSS] Plugins Release
Shaz giving you access at the moment, should be done in 5 minutes On Sun, Dec 11, 2016 at 5:37 PM Shazron wrote: > Hi Steve Gill and/or Carlos Santana -- please give me write access to these > npm modules below. Publishing is stalled until I get permissions. > > cordova-plugin-battery-status > csantanapr > stevegill > cordova-plugin-camera > csantanapr > stevegill > cordova-plugin-console > csantanapr > stevegill > cordova-plugin-contacts > csantanapr > stevegill > cordova-plugin-device > csantanapr > stevegill > cordova-plugin-device-motion > csantanapr > stevegill > cordova-plugin-device-orientation > csantanapr > stevegill > cordova-plugin-dialogs > csantanapr > stevegill > cordova-plugin-file > kotikov.vladimir > csantanapr > stevegill > cordova-plugin-file-transfer > nikhilkh > csantanapr > stevegill > cordova-plugin-geolocation > csantanapr > stevegill > cordova-plugin-globalization > csantanapr > stevegill > cordova-plugin-legacy-whitelist > csantanapr > stevegill > cordova-plugin-media > kotikov.vladimir > csantanapr > stevegill > cordova-plugin-media-capture > csantanapr > stevegill > cordova-plugin-network-information > csantanapr > stevegill > cordova-plugin-screen-orientation > gbenvenuti > stevegill > tony-- > cordova-plugin-splashscreen > kotikov.vladimir > csantanapr > stevegill > cordova-plugin-statusbar > kotikov.vladimir > csantanapr > stevegill > cordova-plugin-test-framework > csantanapr > stevegill > cordova-plugin-vibration > csantanapr > stevegill > cordova-plugin-whitelist > csantanapr > stevegill > > -- > > I already have access to these: > > cordova-plugin-wkwebview-engine > bowserj > kotikov.vladimir > purplecabbage > shazron > csantanapr > stevegill > cordova-plugin-inappbrowser > csantanapr > stevegill > kotikov.vladimir > sgrebnov > shazron > > > On Sun, Dec 11, 2016 at 2:11 PM, Shazron wrote: > > > I've already started https://issues.apache.org/jira/browse/CB-12237 > > > > On Sun, Dec 11, 2016 at 2:01 PM, Shazron wrote: > > > >> One more issue -- cordova-plugin-inappbrowser, my intent is not to call > >> anyone out here (hey I'm the major source of mistakes for this release) > but > >> my intent is to fix the problem. The plugin minor version was > incremented > >> in plugin.xml to 1.6.0 but not incremented in package.json. Thus when > the > >> packaging automation ran, the version had a mismatch, and that this is > >> reflected in cordova-plugin-inappbrowser. > >> > >> https://github.com/apache/cordova-plugin-inappbrowser/commit > >> /cfbd3845a893df647ff39ec3c750804d775a0e57 > >> > >> We should have a version mismatch automation check during release as > well > >> in coho, and/or the tests. > >> > >> So now the problem is, I can't publish cordova-plugin-inappbrowser this > >> release because package.json shows the version is 1.5.1 while > plugin.xml is > >> 1.6.0 (1.6.0 is correct). > >> > >> I will have to omit cordova-plugin-inappbrowser in this release, and put > >> out another cordova plugins release which includes: > >> > >> 1) Updates in cordova-plugin-battery-status that we discussed > >> 2) The package.json update in cordova-plugin-inappbrowser (same version, > >> 1.6.0) > >> > >> > >> > >> > >> > >> > >> > >> On Sun, Dec 11, 2016 at 11:32 AM, Shazron wrote: > >> > >>> I screwed up the release notes for each plugin (RELEASENOTES.md) in > each > >>> plugin repo. I'll fix it after release, but will fix it for the blog > post: > >>> https://issues.apache.org/jira/browse/CB-12236 > >>> > >>> On Thu, Dec 8, 2016 at 9:03 PM, wrote: > >>> > >>>> Just replying to it from my apache address to bump it up from your > spam > >>>> folders, guys. I'll cast my +1 today. > >>>> > >>>> -Original Message- > >>>> From: Michael Braude [mailto:mbra...@microsoft.com] > >>>> Sent: Thursday, December 8, 2016 10:09 PM > >>>> To: dev@cordova.apache.org > >>>> Subject: RE: [DISCUSS] Plugins Release
Re: Carlos MIA
Haha true thanks Shaz for the kind words :-) On Wed, Aug 17, 2016 at 9:37 PM Shazron wrote: > Hey Carlos, > Appreciate your contributions to the community! Sorry to see you going > away... I'm sure you'll be back, a commit here and there, a PMC vote maybe. > However, when you're in Cordova, you are in for life, sorry! :P > > (the commit bit will always be there, I don't think we have ever removed > anyone) > > > > On Wed, Aug 17, 2016 at 6:31 PM, Carlos Santana > wrote: > > > Man this sucks but I have to admit that I have being missing in action > and > > have to realize I can't dedicate the time I would like to Apache Cordova. > > > > This burns me because Cordova have become a second family to me :-( > > > > I recently got re-assigned out from IBM MobileFirst (aka Worklight) in to > > IBM Bluemix to joined a team building a Serverless platform (OpenWhisk), > I > > will still be working on Developer User Experience but covering more than > > tools for mobile developers. > > > > The good thing is that OpenWhisk is an open source project so I will > > continue spending time working on OSS tools for developers. > > > > I still read the mailing list and hang out in Slack from time to time. > > > > As always you can reach me directly via email or Twitter or any other > > means. > > > > I love the passion of this community and the people that makes so, > > community comes before code as some of you have discover it's the success > > of an open project. > > > > Wow! like always I was not expecting to write another manifesto, "just > > wanted to say I'm being super busy on a new project and it sucks that I > > can't spend more time on Cordova for now" > > > > --Carlos > > @csantanapr > > >
Carlos MIA
Man this sucks but I have to admit that I have being missing in action and have to realize I can't dedicate the time I would like to Apache Cordova. This burns me because Cordova have become a second family to me :-( I recently got re-assigned out from IBM MobileFirst (aka Worklight) in to IBM Bluemix to joined a team building a Serverless platform (OpenWhisk), I will still be working on Developer User Experience but covering more than tools for mobile developers. The good thing is that OpenWhisk is an open source project so I will continue spending time working on OSS tools for developers. I still read the mailing list and hang out in Slack from time to time. As always you can reach me directly via email or Twitter or any other means. I love the passion of this community and the people that makes so, community comes before code as some of you have discover it's the success of an open project. Wow! like always I was not expecting to write another manifesto, "just wanted to say I'm being super busy on a new project and it sucks that I can't spend more time on Cordova for now" --Carlos @csantanapr
Re: On vacation
Felicidades y disfruta tu boda !!! "Congratulations and enjoy" - Carlos Santana @csantanapr > On Aug 4, 2016, at 6:17 AM, julio cesar sanchez > wrote: > > Hello all, > > Tomorrow I'm getting married and after that I will be on my honeymoon until > the 22th, so I won't be online for a while. > > I have 3 PRs pending review and/or merge. > > > https://github.com/apache/cordova-plugin-contacts/pull/131 > https://github.com/apache/cordova-ios/pull/239 > https://github.com/phonegap/phonegap-plugin-barcodescanner/pull/302 (not > core plugin but some contributors are on this list) > > So if any of you can review and/or merge them I'll be grateful. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Create an Issue Collector to reduce friction in filing issues
I think it's a good idea overall . Can it be a website/form that fully control the full implementation? Food for thought: - Make it very short with key fields (versions, platform?, plugin?, device?, steps with sample code) - Can we require captcha for anonymous? - Can we offer auth with github? (At least give us some id) - Carlos Santana @csantanapr > On Jun 19, 2016, at 2:52 AM, Shazron wrote: > > https://issues.apache.org/jira/browse/CB-11454 > > Pro: > We can get users to file an issue easily by pointing them to our form > (which will not require a login). > > Con: > Since it is an anonymous form, potential for spammers will increase. > > Thoughts? - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [Discuss] Why was device.name removed from the device-plugin?
I think this belongs in user community plugin maybe a cordova-plugin-device-nickname - Carlos Santana @csantanapr > On Jun 17, 2016, at 10:25 PM, Kerri Shotts wrote: > > -1 to using Bluetooth to get the device name. That would add an additional > permission (AFAICT) that is hard to justify to an end user, and which would > be added to a good number of Cordova apps intending only to use the device > plugin to implement platform-specific features or workarounds. > I agree with Joe -- this is best in a separate plugin. That give the dev a > choice if they can justify the extra permission, and the potential headache > that comes with arbitrary device names (or lack thereof). > My two cents, anyway. :) > ~Kerri > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Nightly build #36 for cordova has succeeded!
Jenkins blue moons š +1 - Carlos Santana @csantanapr > On Jun 9, 2016, at 11:07 PM, Shazron wrote: > > I like how Jenkins is all happy <3 > > On Thu, Jun 9, 2016 at 7:54 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> Nightly build #36 for cordova has succeeded! >> The latest nightly has been published and you can try it out with 'npm i >> -g cordova@nightly' >> >> For details check build console at >> https://builds.apache.org/job/cordova-nightly/36/consoleFull >> >> - >> Jenkins for Apache Cordova >> >> >> - >> 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: [DRAFT] Cordova Board Report for June 2016
LGTM - Carlos Santana @csantanapr > On Jun 8, 2016, at 7:29 PM, Shazron wrote: > > https://github.com/cordova/apache-board-reports/blob/master/2016/2016-06.md > > Let me know of any edits, or anything I missed. > I'm aiming to send this by EOD today or early tomorrow. > > Thanks! - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [FYI] If you are using Gmail, emails from microsoft.com may be in your Spam folder
thanks, I had a few there, how do I tell Inbox that it's not spam? On Wed, Jun 1, 2016 at 4:57 PM Steven Gill wrote: > Wow, I've missed a ton of messages > > On Wed, Jun 1, 2016 at 1:42 PM, Shazron wrote: > > > If you feel you are missing emails in a thread -- it has happened a few > > times to me from microsoft.com senders, check your Spam folder. > > > > "Why is this message in Spam? It has a from address in microsoft.com but > > has failed microsoft.com's required tests for authentication" (see > > attached screenshot). > > > > Learn more goes to: https://support.google.com/mail/answer/1366858 > > > > Not sure why this is happening. > > > > > > [image: Inline image 1] > > >
Re: [DISCUSS] CLI Templates
Using a subdir makes a clear separation between final template files vs. files associated with tooling, tests, packaging - Carlos Santana @csantanapr > On May 31, 2016, at 7:37 PM, Jesse wrote: > > `cordova create` is destructive by nature. > Anything and everything required by the templated app should be part of > what is copied. Our current blind folder copy needs to be more intelligent. > I would prefer that template files be in a sub-dir, much like they are in > each platform. > > Simon and I faced a similar situation with making a plugin template[1] > While only half baked at this point, the file structure is relevant I think. > > [1] https://github.com/phonegap/phonegap-plugin-template > > > > @purplecabbage > risingj.com > >> On Tue, May 31, 2016 at 4:18 PM, Tommy Williams wrote: >> >> .npmignore can help with some of those unwanted files, but not allā¦ >> >> However, what happens in the circumstance when the template _does_ need a >> package.json file, such as the react-hot-loader template Jed and I made? It >> has npm dips and npm scripts that are vital to how it works in its >> package,json. We canāt just omit files, Similarly, a template might include >> hooks and merges as well. >> >> - tommy >> >> >>> On 1 Jun 2016, at 8:22 AM, Carlos Santana wrote: >>> >>> I opened a JIRA for ignoring .git >>> Don't have it handy on mobile now >>> >>> Best practice: >>> 1. To use subdir feature to specify dir to use via main module >>> 2. To follow npm best practices when publishing to npm (i.e. do not >> include everything, only the minimum required) >>> >>> >>> - Carlos Santana >>> @csantanapr >>> >>>> On May 31, 2016, at 6:10 PM, Steven Gill >> wrote: >>>> >>>> Sorry to bring up a old thread instead of starting a new one but I >> thought >>>> the context might be relevant. >>>> >>>> Currently, template pretty much copies over all of the files. I see >> this as >>>> a problem. >>>> >>>> Example [1]. When you add a template, its package.json gets copied into >>>> your app. I don't think we want that to happen right? >>>> >>>> Other files that are getting copied but shouldn't: >>>> - RELEASENOTES.md >>>> - README.md >>>> - .git (if you do it locally or f >>>> - NOTICE >>>> - LICENSE >>>> - COPYWRIGHT >>>> >>>> Files we want: >>>> - config.xml >>>> - .gitignore >>>> - .npmignore ? >>>> - node_modules? >>>> - platforms/plugins (if present) >>>> - hooks >>>> - merges >>>> >>>> templates can provide additional info by setting a subdirectory in their >>>> package.json for where the template files live. >>>> >>>> [1] https://issues.apache.org/jira/browse/CB-11344. >>>> >>>> Thoughts? >>>> >>>> >>>> >>>> On Fri, Dec 11, 2015 at 7:09 AM, Carlos Santana >>>> wrote: >>>> >>>>> Oh I'm late on this thread. >>>>> >>>>> Latest code is in master cordova-cli and cordova-lib >>>>> you have to link lib to cli to get it to show up. >>>>> >>>>> if you are lazy like me you can do "npm install -g >>>>> csantanapr/cordova-cli-dev" >>>>> To see the help "cordova help create" >>>>> --template= ... use a custom template located >>>>> locally, in NPM, or GitHub. >>>>> Options: >>>>> --template= ... use a custom template >>>>> located locally, in NPM, or GitHub. >>>>> --copy-from|src= .. deprecated, use >>>>> --template instead. >>>>> --link-to= symlink to custom www >>>>> assets without creating a copy. >>>>> >>>>> The goal is to help people getting started by using a package from npm >> as >>>>> starting point, I see the samples that Raymond produces being used >> with the >>>>> --template flag for novice users to get a sample running faster. also >>>>> opening the door for web frameworks to have their cordova template in >> npm, >>>>> or plugin creators to share templates that uses their plugin, and
Re: [DISCUSS] CLI Templates
package.json should be ignore also is fetching template via npm If you want to include a package.json then use the subdir feature and include the package.json inside the subdir On Tue, May 31, 2016 at 7:18 PM Tommy Williams wrote: > .npmignore can help with some of those unwanted files, but not allā¦ > > However, what happens in the circumstance when the template _does_ need a > package.json file, such as the react-hot-loader template Jed and I made? It > has npm dips and npm scripts that are vital to how it works in its > package,json. We canāt just omit files, Similarly, a template might include > hooks and merges as well. > > - tommy > > > > On 1 Jun 2016, at 8:22 AM, Carlos Santana wrote: > > > > I opened a JIRA for ignoring .git > > Don't have it handy on mobile now > > > > Best practice: > > 1. To use subdir feature to specify dir to use via main module > > 2. To follow npm best practices when publishing to npm (i.e. do not > include everything, only the minimum required) > > > > > > - Carlos Santana > > @csantanapr > > > >> On May 31, 2016, at 6:10 PM, Steven Gill > wrote: > >> > >> Sorry to bring up a old thread instead of starting a new one but I > thought > >> the context might be relevant. > >> > >> Currently, template pretty much copies over all of the files. I see > this as > >> a problem. > >> > >> Example [1]. When you add a template, its package.json gets copied into > >> your app. I don't think we want that to happen right? > >> > >> Other files that are getting copied but shouldn't: > >> - RELEASENOTES.md > >> - README.md > >> - .git (if you do it locally or f > >> - NOTICE > >> - LICENSE > >> - COPYWRIGHT > >> > >> Files we want: > >> - config.xml > >> - .gitignore > >> - .npmignore ? > >> - node_modules? > >> - platforms/plugins (if present) > >> - hooks > >> - merges > >> > >> templates can provide additional info by setting a subdirectory in their > >> package.json for where the template files live. > >> > >> [1] https://issues.apache.org/jira/browse/CB-11344. > >> > >> Thoughts? > >> > >> > >> > >> On Fri, Dec 11, 2015 at 7:09 AM, Carlos Santana > >> wrote: > >> > >>> Oh I'm late on this thread. > >>> > >>> Latest code is in master cordova-cli and cordova-lib > >>> you have to link lib to cli to get it to show up. > >>> > >>> if you are lazy like me you can do "npm install -g > >>> csantanapr/cordova-cli-dev" > >>> To see the help "cordova help create" > >>> --template= ... use a custom template located > >>> locally, in NPM, or GitHub. > >>> Options: > >>> --template= ... use a custom template > >>> located locally, in NPM, or GitHub. > >>> --copy-from|src= .. deprecated, use > >>> --template instead. > >>> --link-to= symlink to custom www > >>> assets without creating a copy. > >>> > >>> The goal is to help people getting started by using a package from npm > as > >>> starting point, I see the samples that Raymond produces being used > with the > >>> --template flag for novice users to get a sample running faster. also > >>> opening the door for web frameworks to have their cordova template in > npm, > >>> or plugin creators to share templates that uses their plugin, and > declare > >>> the plugin in config.xml > >>> > >>> 1. Omar > >>> what you describe in your list what was implemented > >>> The only thing, that was not implemented because was not in the > proposal > >>> and not discuss was ~/.cordova/config.json > >>> > >>> I didn't added because I think there should be a better architecture > for > >>> config. That's another proposal I'm thinking on doing but it looks > like how > >>> npm does config > >>> For example have "cordova config" cli > >>> cordova config set template=my-app-hello > >>> cordova config ls > >>> and so... > >>> so default configs can be override using the CLI > >>> > >>> 2. Dmitry > >>> Let's have a hangout and let's, talk because I don
Re: [DISCUSS] CLI Templates
I opened a JIRA for ignoring .git Don't have it handy on mobile now Best practice: 1. To use subdir feature to specify dir to use via main module 2. To follow npm best practices when publishing to npm (i.e. do not include everything, only the minimum required) - Carlos Santana @csantanapr > On May 31, 2016, at 6:10 PM, Steven Gill wrote: > > Sorry to bring up a old thread instead of starting a new one but I thought > the context might be relevant. > > Currently, template pretty much copies over all of the files. I see this as > a problem. > > Example [1]. When you add a template, its package.json gets copied into > your app. I don't think we want that to happen right? > > Other files that are getting copied but shouldn't: > - RELEASENOTES.md > - README.md > - .git (if you do it locally or f > - NOTICE > - LICENSE > - COPYWRIGHT > > Files we want: > - config.xml > - .gitignore > - .npmignore ? > - node_modules? > - platforms/plugins (if present) > - hooks > - merges > > templates can provide additional info by setting a subdirectory in their > package.json for where the template files live. > > [1] https://issues.apache.org/jira/browse/CB-11344. > > Thoughts? > > > > On Fri, Dec 11, 2015 at 7:09 AM, Carlos Santana > wrote: > >> Oh I'm late on this thread. >> >> Latest code is in master cordova-cli and cordova-lib >> you have to link lib to cli to get it to show up. >> >> if you are lazy like me you can do "npm install -g >> csantanapr/cordova-cli-dev" >> To see the help "cordova help create" >> --template= ... use a custom template located >> locally, in NPM, or GitHub. >> Options: >>--template= ... use a custom template >> located locally, in NPM, or GitHub. >>--copy-from|src= .. deprecated, use >> --template instead. >>--link-to= symlink to custom www >> assets without creating a copy. >> >> The goal is to help people getting started by using a package from npm as >> starting point, I see the samples that Raymond produces being used with the >> --template flag for novice users to get a sample running faster. also >> opening the door for web frameworks to have their cordova template in npm, >> or plugin creators to share templates that uses their plugin, and declare >> the plugin in config.xml >> >> 1. Omar >> what you describe in your list what was implemented >> The only thing, that was not implemented because was not in the proposal >> and not discuss was ~/.cordova/config.json >> >> I didn't added because I think there should be a better architecture for >> config. That's another proposal I'm thinking on doing but it looks like how >> npm does config >> For example have "cordova config" cli >> cordova config set template=my-app-hello >> cordova config ls >> and so... >> so default configs can be override using the CLI >> >> 2. Dmitry >> Let's have a hangout and let's, talk because I don't understand what is the >> problem that --template is causing, >> I don't understand if you don't want the flag present, or the >> implementation, or you want to keep --copy-from as it is today. >> Email is not helping to communicate what is what you think that is broken >> >> 3. Simon >> There is no much documentation other than the help, and mentioned in the >> docs. >> Will love some help feedback and help on docs for this . >> >> https://github.com/apache/cordova-docs/blob/master/www/docs/en/dev/guide/cli/index.md >> https://github.com/apache/cordova-cli/blob/master/doc/create.txt#L14 >> >> Finally nothing is writing in stone, we can change, remove, add to this as >> we iterate. >> >> I thought I follow the our community practices as best I understood. >> Wrote a proposal, communicated in the mailing list, got feedback to change >> the original proposal to not exclude platforms/plugins and other changes. >> had pointers to PR, JIRA, proposal, discussion, waited for feedback on PR, >> gave a heads up on that there was no more feedback and everything that was >> discuss was implemented. >> >> I saw Dmitry'ss comments just after we merge, but I try to give enough >> heads up. And will like to understand better what are his concerns. >> >> >> On Thu, Dec 10, 2015 at 6:53 PM Simon MacDonald >> >> wrote: >> >>> Are there docs checked in anywhere that describe how to use
Re: [DISCUSS] Cordova-Android 5.2.0 Release
+1 - Carlos @csantanapr > On May 25, 2016, at 3:08 PM, Shazron wrote: > > +1 > > Release often > >> On Wed, May 25, 2016 at 10:33 AM, Joe Bowser wrote: >> >> Hey >> >> I know that we haven't done a minor release for a few months for Android, >> and I think that we have enough worthwhile changes in Android that we >> should probably do a release soon. If possible, I would like for us to do >> a 5.2.0 release with the versioning fix, and the other build script fixes >> that have been done recently. There's not a lot of commits, but I do think >> what we do have is worthy of being released. >> >> What do people think? >> >> Joe >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Yet another Cordova-Android 6.0.x release thread, and another 5.x release soon
Hehe thanks for the clarification it crossed my mind that we were going to ship some type of dynamic cordova runtime to the playstore for Devs to pickup AAR makes more sense :-) - Carlos @csantanapr > On May 25, 2016, at 11:51 AM, Joe Bowser wrote: > > That was a typo. > > On Wed, May 25, 2016 at 8:50 AM, Simon MacDonald > wrote: > >> LGTM too. >> >> Although is "Cordova-Android as a distributable APK" supposed to be >> "Cordova-Android >> as a distributable AAR"? >> >> >> Simon Mac Donald >> http://hi.im/simonmacdonald >> >> On Tue, May 24, 2016 at 4:24 PM, Carlos Santana >> wrote: >> >>> LGTM >>> I don't think Android N is going to change that much like you said. >>> >>> Let's move forward as usual , create a branch 6.x on main repo and start >>> that release stream >>> >>> Start landing features from the list below and have a board to track was >>> left. When it's done it's done when ever that's it and we release >>> regardless of official date of Android N (it might along or be bit after) >>> >>> And as normal process we need to care and feed both branches (master & >>> 6.x) having them green and CI testing as Android N builds come out. >>> >>> Any plugins need a 6.x branch corresponding to cordova-android@6.x >>> branch, I don't think so but is good to ask. >>> >>> - Carlos >>> @csantanapr >>> >>>> On May 24, 2016, at 4:07 PM, Joe Bowser wrote: >>>> >>>> I picked September because it's after when Android N is released. The >>>> items on the list don't depend on each other. >>>> >>>> Also, we use semver so us breaking an API or making a major breaking >>> change >>>> means a major bump. Not all of these are API breaking, and in fact >> only >>>> the Android Studio project structure and the Thread-Safe bridge breaks >>>> stuff. >>>> >>>> I don't want to make a 6.0 and a 7.0 for the two major breaking changes >>> and >>>> would rather group the two together since they're both related but not >>>> dependent. >>>> >>>> >>>>> On Tue, May 24, 2016, 12:58 PM Carlos Santana >>> wrote: >>>>> >>>>> Why the Sept. date? >>>>> >>>>> Because Android N actually exists in August sometime, but I don't >> have >>> a >>>>> solid date. >>>>> >>>>> >>>>> All these items depend on each other and will take until Sept. to get >> it >>>>> implemented? >>>>> >>>>> No, but >>>>> >>>>> Each of them break APIs that required a major bump version? >>>>> >>>>> Can we implement one first let's say June call it 6.0 and continue >>>>> releasing each month or as features get implemented 6.1, 6.2, etc. . >>>>> >>>>> Which will be the first one that make most sense to implement? New >>> Studio >>>>> Project? >>>>> >>>>> - Carlos >>>>> @csantanapr >>>>> >>>>>> On May 24, 2016, at 1:43 PM, Joe Bowser wrote: >>>>>> >>>>>> Hey >>>>>> >>>>>> Since Google IO didn't really throw any new features at us, and since >>>>>> Google hinted at Android N being released at the end of August, do >>> people >>>>>> think that aiming for a Cordova-Android 6.0.x release in September >> with >>>>> the >>>>>> following features makes sense: >>>>>> >>>>>> * Android Studio project structure >>>>>> * Android N Multi-Window Support >>>>>> * Thread-Safe bridge by default >>>>>> * Cordova-Android as a distributable APK >>>>>> >>>>>> I know that we had an earlier thread about this, but now that IO is >>> over, >>>>>> we should probably ramp things up now that we know that we're not >>> waiting >>>>>> until November for a new version of Android to land. The biggest >>> change >>>>> is >>>>>> the Android Studio project structure, and everything else has been >>>>> sitting >>>>>> in branches for months ready to be merged in. >>>>>> >>>>>> Also, I know a lot of people are waiting for the change to version >>>>> numbers >>>>>> where we don't magically generate version numbers for arch-neutral >> APKs >>>>> as >>>>>> well as other script changes to the build, so I think we should do >>>>> another >>>>>> Cordova release to address those issues soon. >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> Joe >>>>> >>>>> - >>>>> 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: [FYI] New list viewer
Do we need a JIRA to update the website with the new link? http://cordova.apache.org/contact/ - Carlos @csantanapr > On May 24, 2016, at 4:42 PM, Shazron wrote: > > https://lists.apache.org/list.html?dev@cordova.apache.org > > Most importantly, there is a search function, and permalinks to discussions > for reference elsewhere, so we don't have to use Markmail.
Re: [FYI] New list viewer
RIP Mark Mail ? Welcome Pony Mail š“ - Carlos @csantanapr > On May 24, 2016, at 4:42 PM, Shazron wrote: > > https://lists.apache.org/list.html?dev@cordova.apache.org > > Most importantly, there is a search function, and permalinks to discussions > for reference elsewhere, so we don't have to use Markmail. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Yet another Cordova-Android 6.0.x release thread, and another 5.x release soon
LGTM I don't think Android N is going to change that much like you said. Let's move forward as usual , create a branch 6.x on main repo and start that release stream Start landing features from the list below and have a board to track was left. When it's done it's done when ever that's it and we release regardless of official date of Android N (it might along or be bit after) And as normal process we need to care and feed both branches (master & 6.x) having them green and CI testing as Android N builds come out. Any plugins need a 6.x branch corresponding to cordova-android@6.x branch, I don't think so but is good to ask. - Carlos @csantanapr > On May 24, 2016, at 4:07 PM, Joe Bowser wrote: > > I picked September because it's after when Android N is released. The > items on the list don't depend on each other. > > Also, we use semver so us breaking an API or making a major breaking change > means a major bump. Not all of these are API breaking, and in fact only > the Android Studio project structure and the Thread-Safe bridge breaks > stuff. > > I don't want to make a 6.0 and a 7.0 for the two major breaking changes and > would rather group the two together since they're both related but not > dependent. > > >> On Tue, May 24, 2016, 12:58 PM Carlos Santana wrote: >> >> Why the Sept. date? >> >> Because Android N actually exists in August sometime, but I don't have a >> solid date. >> >> >> All these items depend on each other and will take until Sept. to get it >> implemented? >> >> No, but >> >> Each of them break APIs that required a major bump version? >> >> Can we implement one first let's say June call it 6.0 and continue >> releasing each month or as features get implemented 6.1, 6.2, etc. . >> >> Which will be the first one that make most sense to implement? New Studio >> Project? >> >> - Carlos >> @csantanapr >> >>> On May 24, 2016, at 1:43 PM, Joe Bowser wrote: >>> >>> Hey >>> >>> Since Google IO didn't really throw any new features at us, and since >>> Google hinted at Android N being released at the end of August, do people >>> think that aiming for a Cordova-Android 6.0.x release in September with >> the >>> following features makes sense: >>> >>> * Android Studio project structure >>> * Android N Multi-Window Support >>> * Thread-Safe bridge by default >>> * Cordova-Android as a distributable APK >>> >>> I know that we had an earlier thread about this, but now that IO is over, >>> we should probably ramp things up now that we know that we're not waiting >>> until November for a new version of Android to land. The biggest change >> is >>> the Android Studio project structure, and everything else has been >> sitting >>> in branches for months ready to be merged in. >>> >>> Also, I know a lot of people are waiting for the change to version >> numbers >>> where we don't magically generate version numbers for arch-neutral APKs >> as >>> well as other script changes to the build, so I think we should do >> another >>> Cordova release to address those issues soon. >>> >>> Thoughts? >>> >>> Joe >> >> - >> 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: Yet another Cordova-Android 6.0.x release thread, and another 5.x release soon
Why the Sept. date? All these items depend on each other and will take until Sept. to get it implemented? Each of them break APIs that required a major bump version? Can we implement one first let's say June call it 6.0 and continue releasing each month or as features get implemented 6.1, 6.2, etc. . Which will be the first one that make most sense to implement? New Studio Project? - Carlos @csantanapr > On May 24, 2016, at 1:43 PM, Joe Bowser wrote: > > Hey > > Since Google IO didn't really throw any new features at us, and since > Google hinted at Android N being released at the end of August, do people > think that aiming for a Cordova-Android 6.0.x release in September with the > following features makes sense: > > * Android Studio project structure > * Android N Multi-Window Support > * Thread-Safe bridge by default > * Cordova-Android as a distributable APK > > I know that we had an earlier thread about this, but now that IO is over, > we should probably ramp things up now that we know that we're not waiting > until November for a new version of Android to land. The biggest change is > the Android Studio project structure, and everything else has been sitting > in branches for months ready to be merged in. > > Also, I know a lot of people are waiting for the change to version numbers > where we don't magically generate version numbers for arch-neutral APKs as > well as other script changes to the build, so I think we should do another > Cordova release to address those issues soon. > > Thoughts? > > Joe - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Nightly builds for Cordova
Love it +1 Always wanted to be able to $ npm install -g cordova@canary - Carlos @csantanapr > On May 13, 2016, at 5:14 AM, Vladimir Kotikov (Akvelon) > wrote: > > Hi list > > I've created a proposal for releasing nightly builds for Cordova. Please find > details here: https://github.com/cordova/cordova-discuss/pull/42. > I will appreciate any suggestions and feedback. > > - > Best regards, Vladimir > > > - > 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] Cordova tools release
Do we fully support node6 now? If we do might be good to highlight in blog post - Carlos @csantanapr > On May 12, 2016, at 5:00 PM, Steven Gill wrote: > > Excellent! I shall proceed. > > The website will also get updated when I do the release blog post. > > Cheers, > -Steve > >> On Thu, May 12, 2016 at 12:52 PM, Mefire O. wrote: >> >> Hey Steve, >> Telemetry has been merged in! >> We can move forward with the release process. >> >> We'll also have to initiate a docs/website release, as they host our >> privacy policy. >> Raghav will help with that. >> >> Thanks for your patience, All. >> >> Thanks, >> Omar Mefire >> >> -Original Message- >> From: Mefire O. [mailto:ommen...@microsoft.com] >> Sent: Tuesday, May 10, 2016 5:25 PM >> To: dev@cordova.apache.org >> Subject: RE: [DISCUSS] Cordova tools release >> >> I expect it to be merged in by tomorrow EOD or day Thursday morning. >> If it's still not merged in by then, I wouldn't want to hold the release >> any longer. >> >> Thanks, >> Omar Mefire >> >> -Original Message- >> From: Steven Gill [mailto:stevengil...@gmail.com] >> Sent: Tuesday, May 10, 2016 2:39 PM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Cordova tools release >> >> When do you expect to merge it in? >> >>> On Tue, May 10, 2016 at 2:19 PM, Mefire O. wrote: >>> >>> I'd like to get the telemetry feature out with this release. >>> >>> Thanks, >>> Omar Mefire >>> >>> -Original Message- >>> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] >>> Sent: Tuesday, May 10, 2016 12:47 AM >>> To: dev@cordova.apache.org >>> Subject: RE: [DISCUSS] Cordova tools release >>> >>> +1 >>> >>> Thanks for handling cordova-common release - there is probably not >>> much sense in releasing it separately (as I was planning initially) >>> when other components also need to be released. >>> >>> - >>> Best regards, Vladimir >>> >>> -Original Message- >>> From: julio cesar sanchez [mailto:jcesarmob...@gmail.com] >>> Sent: Tuesday, May 10, 2016 1:14 AM >>> To: dev@cordova.apache.org >>> Subject: Re: [DISCUSS] Cordova tools release >>> >>> +1 >>> >>> El martes, 10 de mayo de 2016, Shazron escribiĆ³: >>> +1 On Mon, May 9, 2016 at 12:32 PM, Steven Gill >>> > wrote: > Any objections or concerns? > > Doing a cli, lib, plugman, common and fetch release. > > -Steve >>> >>> - >>> 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: [DISCUSS] Cordova tools release
+1 Choo choo !! - Carlos @csantanapr > On May 9, 2016, at 3:32 PM, Steven Gill wrote: > > Any objections or concerns? > > Doing a cli, lib, plugman, common and fetch release. > > -Steve - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [Android] Ending support for Ice Cream Sandwich?
+1 I just double check and next release of IBM MFP we will support Jelly Bean and up On Fri, May 6, 2016 at 9:08 AM Raymond Camden wrote: > +1 > > On Fri, May 6, 2016 at 6:19 AM, Simon MacDonald > wrote: > > +1 to dropping support for ICS in the next major release of > cordova-android. > > > > Simon Mac Donald > > http://hi.im/simonmacdonald > > > > On Fri, May 6, 2016 at 12:35 AM, julio cesar sanchez < > jcesarmob...@gmail.com > >> wrote: > > > >> ICS is on 2% of android devices, even lower than gingerbread (2,2%) > >> > >> So +1 to deprecating > >> > >> http://developer.android.com/about/dashboards/index.html#Platform > >> El 6 may. 2016 8:57 a. m., "Joe Bowser" escribiĆ³: > >> > >> > Hey > >> > > >> > So, it's been a while, but it looks like we should really drop support > >> for > >> > ICS, because Crosswalk is dropping support for ICS. > >> > > >> > https://crosswalk-project.org/blog/deprecate-40.html > >> > > >> > So, yeah, I think we should drop support for ICS. I know it's been a > >> "Meh, > >> > why not?" thing for people to support for a while and there wasn't a > >> super > >> > strong case for dropping it, but now that we can't use Crosswalk to > fix > >> our > >> > WebView woes, I think it's time to put this thing at rest and move on. > >> > > >> > Thoughts? > >> > > >> > Joe > >> > > >> > > > > -- > === > Raymond Camden, Developer Advocate for StrongLoop 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 > >
Re: [DISCUSS] Faster incremental builds
+1 also minor bump - Carlos @csantanapr > On Apr 27, 2016, at 5:24 PM, Jason Ginchereau wrote: > > OK, I think there is a solution that will make everyone happy, while > maintaining compatibility with existing after_prepare hooks: An incremental > prepare can copy both files that are newer AND FILES THAT ARE OLDER than the > target files in the platform's www directory, while skipping any files which > have an identical last-modified time. That way, any after_prepare hook that > modifies a prepared file will still see the file refreshed on every prepare, > as it does today, while all the unchanged files will be skipped, greatly > speeding up the prepare. > > With this approach, I think there is no need to put the incremental prepare > behind a --incremental option; it can just be the default behavior. (I am > still adding prepared files to cordova clean also.) And since this shouldn't > break anything, it won't require a major version bump. But I suppose it > should be a minor version bump, since it's new functionality. > > Jason > > > -Original Message- > From: Jason Ginchereau [mailto:jason...@microsoft.com] > Sent: Tuesday, April 26, 2016 9:39 AM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Faster incremental builds > > I don't understand how adding a file list to the hook parameters will help > solve this problem. Any hook that currently fails after an incremental > prepare would need to be updated either way. It would be simpler to just > update it to correctly handle the case when a file wasn't updated by prepare. > > We still don't have any real examples of hooks where this is a problem, do > we? But it still seems safest to save this change for a major version update, > unfortunately. > > Jason > > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Friday, April 22, 2016 5:03 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Faster incremental builds > > Why your saying is more complicated? > Complicated for hook authors? > for the hooks that don't need they don't have to do anything just ignore the > argument in context. > > "cordova prepare --clean" == "cordova clean && cordova prepare" > > > > - Carlos > @csantanapr > >> On Apr 22, 2016, at 7:45 PM, Jason Ginchereau wrote: >> >> I don't think making the after_prepare hook API more complicated is a good >> design. Instead can we just document that after_prepare hooks should be >> designed to handle the files being copied only sometimes? Most of them >> probably are anyway, because Cordova never made an explicit guarantee about >> the files being fresh every time the hook is called. Anyway I guess it could >> still be considered a breaking change so maybe it should trigger a >> major-version bump? >> >> I don't understand what you are suggesting with "cordova prepare --clean". >> >> -Original Message- >> From: Carlos Santana [mailto:csantan...@gmail.com] >> Sent: Thursday, April 21, 2016 17:16 >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Faster incremental builds >> >> I guess it's fine to have default to be faster, we just need to pass the >> files to be copied to feed the hook to be aware. It's kind of a break API on >> CLI so maybe CLI 7.x but not sure. >> >> Also for folks that want the conversation approach with one command we can >> also have a flag --clean "cordova prepare --clean" >> >> >> - Carlos >> @csantanapr >> >>> On Apr 21, 2016, at 7:42 PM, Jason Ginchereau >>> wrote: >>> >>> Thanks Carlos, that's a good point. >>> >>> The Ionic add_platform_class hook >>> (https://github.com/driftyco/ionic-package-hooks) actually would be fine; >>> it doesn't do anything if the CSS class to be added is already there. >>> >>> But I guess it's possible some other after_prepare hooks might not be as >>> smart. I'm not sure what to do about that. >>> >>> >>> -Original Message- >>> From: Carlos Santana [mailto:csantan...@gmail.com] >>> Sent: Thursday, April 21, 2016 2:25 PM >>> To: dev@cordova.apache.org >>> Subject: Re: [DISCUSS] Faster incremental builds >>> >>> The only thing to watch out is folks modified files during after_prepare >>> event, then they will be broken if the file have not changed and they >>> modified/add con
Re: help with "npm test" for cordova-lib
It's jasmine test that is failing [1]
Does this means that jasmine tests are not running in a continuously? Any
reason why are they not running in Travis?
I can't figure out what is the test trying to test:
it('should successfully add a plugin using relative path when running from
subdir inside of project',
So I need some help trying to fix it.
[1]:
https://github.com/apache/cordova-lib/blob/master/cordova-lib/spec-cordova/plugin.spec.js#L171
On Mon, Apr 25, 2016 at 12:51 PM Jesse wrote:
> Travis is running this:
> - git clone https://github.com/apache/cordova-js --depth 10
> - cd cordova-lib
> - npm link ../cordova-js
> - npm link ../cordova-common
> - npm link ../cordova-serve
> - npm install
> - "(cd ../cordova-common && npm test)"
> - "npm run ci"
>
> There are a lot of different things that could affect the tests, which
> cordova-js&|common&|serve you have installed/linked and so on.
> Travis is essentially doing 'npm run ci' which does not run jasmine, so the
> issue is probably a failing jasmine test.
> Can you try running 'npm run ci' and seeing if that passes?
>
>
>
> @purplecabbage
> risingj.com
>
> On Sat, Apr 23, 2016 at 1:53 PM, Carlos Santana
> wrote:
>
> > I do't get it then, Travis is green, so Travis not running same test
> suite
> > as "npm test"?
> >
> > On Fri, Apr 22, 2016 at 9:11 PM Shazron wrote:
> >
> > > I'm seeing the same. Using node 0.12.7
> > >
> > >
> > > On Fri, Apr 22, 2016 at 12:44 PM, Carlos Santana >
> > > wrote:
> > >
> > > > I'm seeing 2 test failures when I do "npm test"
> > > >
> > > > Anyone seeing the same? Wonder what I have setup wrong here:
> > > >
> > > > Here is a paste http://pastebin.com/4E4c40X5 of my output
> > > >
> > > > I thought it was node 5, but then swift to node 4 and the same.
> > > > This is after making sure all npm links are correct with "coho
> > npm-link"
> > > >
> > >
> >
>
Re: help with "npm test" for cordova-lib
I do't get it then, Travis is green, so Travis not running same test suite as "npm test"? On Fri, Apr 22, 2016 at 9:11 PM Shazron wrote: > I'm seeing the same. Using node 0.12.7 > > > On Fri, Apr 22, 2016 at 12:44 PM, Carlos Santana > wrote: > > > I'm seeing 2 test failures when I do "npm test" > > > > Anyone seeing the same? Wonder what I have setup wrong here: > > > > Here is a paste http://pastebin.com/4E4c40X5 of my output > > > > I thought it was node 5, but then swift to node 4 and the same. > > This is after making sure all npm links are correct with "coho npm-link" > > >
Re: [DISCUSS] Faster incremental builds
Why your saying is more complicated? Complicated for hook authors? for the hooks that don't need they don't have to do anything just ignore the argument in context. "cordova prepare --clean" == "cordova clean && cordova prepare" - Carlos @csantanapr > On Apr 22, 2016, at 7:45 PM, Jason Ginchereau wrote: > > I don't think making the after_prepare hook API more complicated is a good > design. Instead can we just document that after_prepare hooks should be > designed to handle the files being copied only sometimes? Most of them > probably are anyway, because Cordova never made an explicit guarantee about > the files being fresh every time the hook is called. Anyway I guess it could > still be considered a breaking change so maybe it should trigger a > major-version bump? > > I don't understand what you are suggesting with "cordova prepare --clean". > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Thursday, April 21, 2016 17:16 > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Faster incremental builds > > I guess it's fine to have default to be faster, we just need to pass the > files to be copied to feed the hook to be aware. It's kind of a break API on > CLI so maybe CLI 7.x but not sure. > > Also for folks that want the conversation approach with one command we can > also have a flag --clean "cordova prepare --clean" > > > - Carlos > @csantanapr > >> On Apr 21, 2016, at 7:42 PM, Jason Ginchereau wrote: >> >> Thanks Carlos, that's a good point. >> >> The Ionic add_platform_class hook >> (https://github.com/driftyco/ionic-package-hooks) actually would be fine; it >> doesn't do anything if the CSS class to be added is already there. >> >> But I guess it's possible some other after_prepare hooks might not be as >> smart. I'm not sure what to do about that. >> >> >> -Original Message- >> From: Carlos Santana [mailto:csantan...@gmail.com] >> Sent: Thursday, April 21, 2016 2:25 PM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Faster incremental builds >> >> The only thing to watch out is folks modified files during after_prepare >> event, then they will be broken if the file have not changed and they >> modified/add content to the file a second time. >> >> To make this work the hook event will need to inform batch/node and plugins >> hooks on before_prepare and after_prepare the list of files that are going >> to be copy, so the hook owner can know not to modified the file if their >> file is not I the list. >> >> One real use case is Ionic and I think MobileFirst. >> For MobileForst I think we don't modified I think we just recreate new >> file ok every prepare >> >> For Ionic they edit the index.html to a class to to the body element >> to for platform identification >> >> - Carlos >> @csantanapr >> >>> On Apr 21, 2016, at 5:12 PM, Jason Ginchereau >>> wrote: >>> >>> If "cordova clean" would also take care of deleting the files copied by >>> prepare, then I'd be confident in making prepare incremental by default. >>> Then if anyone was ever concerned about whether the incremental prepare was >>> doing the right thing, "cordova clean" would be a fairly obvious way to >>> reset the build. I still can't think of a realistic developer scenario >>> where that would be necessary, but it seems like the right thing for a >>> "clean" command to do regardless. >>> >>> So I will work on enhancing the "clean" function for each platform at the >>> same time I enable the incremental prepare. >>> >>> Jason >>> >>> -Original Message- >>> From: Jason Ginchereau [mailto:jason...@microsoft.com] >>> Sent: Wednesday, April 20, 2016 10:00 AM >>> To: dev@cordova.apache.org >>> Subject: RE: [DISCUSS] Faster incremental builds >>> >>> My concern with making this the default behavior is that Cordova >>> prepare doesn't have a corresponding "clean" operation. While there >>> is a "cordova clean" command, it only does a clean for the >>> native-code project (e.g. gradle clean), which doesn't affect the >>> files copied during prepare. I guess this would only be a problem if >>> you did something to give your source files older last-modified >>> times... th
add --depth 1 to all git fetches?
Need feedback I open improvement CB-11144 [1] to see if we can speed up git fetches. It's safe to use --depth 1? I can't recall what exact plugin it was, but I was helping someone on Slack with git fetches and it took for ever for me to get the plugin install. [1] https://issues.apache.org/jira/browse/CB-11144
Re: Apache Con NA May 11-13 in Vancouver, BC
I don't have travel budget, but I can get a room here in NC, but it doesn't make sense for everyone flight over here. I think it would be best to have it where more committers can attend which will be where the Adobians are located :-) On Fri, Apr 22, 2016 at 3:42 PM Ryan J. Salva wrote: > Frankly, the Microsoft committers team would not be able to attend in the > same numbers compared to last year due to budget constraints. Nevertheless, > I'm sure we could send 1-2 people. > > rjs > > Ryan J. Salva | Principal PM Manager > Visual Studio Tools for Apache Cordova > rsa...@microsoft.com > 425 706 5270 office > 206 612 5079 mobile > > -Original Message- > From: Raymond Camden [mailto:raymondcam...@gmail.com] > Sent: Friday, April 22, 2016 2:53 PM > To: dev@cordova.apache.org > Subject: Re: Apache Con NA May 11-13 in Vancouver, BC > > Depending on timing I could. > > On Fri, Apr 22, 2016 at 11:20 AM, Jesse wrote: > > We have a room in SF we could book, if need be. Do other > > teams/committers have budget for travel? > > > > > > -- > === > Raymond Camden, Developer Advocate for StrongLoop at IBM > > Email : raymondcam...@gmail.com > Blog : > https://na01.safelinks.protection.outlook.com/?url=www.raymondcamden.com&data=01%7c01%7crsalva%40microsoft.com%7c45e4cf3feff941f3909e08d36adf4e84%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=P6BIjA5HlAZGfoaHsiCKp8YhlUEMlgRj51exRMrsikI%3d > Twitter: raymondcamden > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
help with "npm test" for cordova-lib
I'm seeing 2 test failures when I do "npm test" Anyone seeing the same? Wonder what I have setup wrong here: Here is a paste http://pastebin.com/4E4c40X5 of my output I thought it was node 5, but then swift to node 4 and the same. This is after making sure all npm links are correct with "coho npm-link"
Re: registry.cordova.io down (Cordova Plugin Registry a.k.a the CPR)
That's not nice Simon, I hope the Ghost of the Registry comes and pull your legs while your are sleeping LOL Seriously Kudos to those involved in the inception and good choices on using noSQL and mapping to an npm registry for future proof. Great Cordovians visionaries !! - Carlos @csantanapr > On Apr 22, 2016, at 7:49 AM, Simon MacDonald > wrote: > > It's dead and I'm glad it's dead. That bastard owed me $20. >> On Apr 21, 2016 23:30, "Kerri Shotts" wrote: >> >> May the registry rest in peace in the ethereal bit bucket in the sky! >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Faster incremental builds
I guess it's fine to have default to be faster, we just need to pass the files to be copied to feed the hook to be aware. It's kind of a break API on CLI so maybe CLI 7.x but not sure. Also for folks that want the conversation approach with one command we can also have a flag --clean "cordova prepare --clean" - Carlos @csantanapr > On Apr 21, 2016, at 7:42 PM, Jason Ginchereau wrote: > > Thanks Carlos, that's a good point. > > The Ionic add_platform_class hook > (https://github.com/driftyco/ionic-package-hooks) actually would be fine; it > doesn't do anything if the CSS class to be added is already there. > > But I guess it's possible some other after_prepare hooks might not be as > smart. I'm not sure what to do about that. > > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Thursday, April 21, 2016 2:25 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Faster incremental builds > > The only thing to watch out is folks modified files during after_prepare > event, then they will be broken if the file have not changed and they > modified/add content to the file a second time. > > To make this work the hook event will need to inform batch/node and plugins > hooks on before_prepare and after_prepare the list of files that are going to > be copy, so the hook owner can know not to modified the file if their file is > not I the list. > > One real use case is Ionic and I think MobileFirst. > For MobileForst I think we don't modified I think we just recreate new file > ok every prepare > > For Ionic they edit the index.html to a class to to the body element to for > platform identification > > - Carlos > @csantanapr > >> On Apr 21, 2016, at 5:12 PM, Jason Ginchereau wrote: >> >> If "cordova clean" would also take care of deleting the files copied by >> prepare, then I'd be confident in making prepare incremental by default. >> Then if anyone was ever concerned about whether the incremental prepare was >> doing the right thing, "cordova clean" would be a fairly obvious way to >> reset the build. I still can't think of a realistic developer scenario where >> that would be necessary, but it seems like the right thing for a "clean" >> command to do regardless. >> >> So I will work on enhancing the "clean" function for each platform at the >> same time I enable the incremental prepare. >> >> Jason >> >> -Original Message- >> From: Jason Ginchereau [mailto:jason...@microsoft.com] >> Sent: Wednesday, April 20, 2016 10:00 AM >> To: dev@cordova.apache.org >> Subject: RE: [DISCUSS] Faster incremental builds >> >> My concern with making this the default behavior is that Cordova >> prepare doesn't have a corresponding "clean" operation. While there is >> a "cordova clean" command, it only does a clean for the native-code >> project (e.g. gradle clean), which doesn't affect the files copied >> during prepare. I guess this would only be a problem if you did >> something to give your source files older last-modified times... then >> a cordova prepare/build/run that was incremental would not pick up the >> older files, and "cordova clean" wouldn't fix it. I was thinking a git >> checkout could do that, but upon investigation it actually doesn't >> reset files' last-modified times. (I guess any source control tools >> shouldn't, as it would mess up any kind of incremental build system.) >> >> Maybe "cordova clean" should also delete the files that are copied by >> prepare? Or maybe there could be something like a "cordova prepare --force" >> flag for the rare case when a non-incremental prepare is needed? Between >> those two I'd prefer making "cordova clean" more thorough; I didn't think of >> that until now. >> >> Jason >> >> -Original Message- >> From: Steven Gill [mailto:stevengil...@gmail.com] >> Sent: Wednesday, April 20, 2016 9:18 AM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Faster incremental builds >> >> Thanks for sharing the stats! Looks like a great improvement! >> >> I'm fine with this going in sans flag if we test it bit more first. >> >> Have your tried it with the --browserify flag? >>> On Apr 20, 2016 7:18 AM, "Victor Sosa" wrote: >>> >>> This is an amazing improvement in Cordova performance. Thanks Jason >
Re: Apache Con NA May 11-13 in Vancouver, BC
Same here no IBM budget :-( - Carlos @csantanapr > On Apr 21, 2016, at 9:09 AM, Homer, Tony wrote: > > FWIW, I checked into the possibility of having Intel host a F2F in Q3. > However, my request was denied for this year :( > > If we can find a host, I'd like to attend! > How about it IBM?! > > :) > >> On 4/18/16, 2:15 PM, "Jesse" wrote: >> >> No, unfortunately the PhoneGap Vancouver office was closed. >> >> >> @purplecabbage >> risingj.com >> >> On Mon, Apr 18, 2016 at 10:53 AM, Ryan J. Salva >> wrote: >> >>> Is there still an Adobe office in Vancover? >>> >>> >>> Ryan J. Salva | Principal PM Manager >>> Visual Studio Tools for Apache Cordova >>> rsa...@microsoft.com >>> 425 706 5270 office >>> 206 612 5079 mobile >>> >>> -Original Message- >>> From: Shazron [mailto:shaz...@gmail.com] >>> Sent: Monday, April 18, 2016 1:51 PM >>> To: dev@cordova.apache.org >>> Subject: Re: Apache Con NA May 11-13 in Vancouver, BC >>> >>> Also, I would recommend an autumn date, where (presumably) everybody will >>> be available. Preferably at one of our contributor sites that hasn't hosted >>> before? >>> >>> We've had Google (Waterloo, ON) and Microsoft (Redmond, WA) previously. >>> >>>> On Mon, Apr 18, 2016 at 11:34 AM, Jesse wrote: >>>> >>>> Vancouver would be awesome! Just not as soon as ApacheCon. >>>> >>>> >>>> @purplecabbage >>>> https://na01.safelinks.protection.outlook.com/?url=risingj.com&data=01 >>>> %7c01%7crsalva%40microsoft.com%7cbb0edb0b618e454eb92008d367b213f1%7c72 >>>> f988bf86f141af91ab2d7cd011db47%7c1&sdata=rS4UBTFrNoY%2bRtI3xRmMzmLSAiR >>>> ksEdFDsbhWSh%2ftYk%3d >>>> >>>> On Mon, Apr 18, 2016 at 8:42 AM, Ryan J. Salva >>>> wrote: >>>> >>>>> Regrettably, Microsoft won't be attending ApacheCon this year either. >>>>> Without critical mass from the other Cordova contributors, it simply >>>>> doesn't make sense (as much as I'd love to visit Vancouver). >>>>> >>>>> Does anyone have a recommended destination, host or occasion for the >>>> F2F? >>>>> >>>>> rjs >>>>> >>>>> >>>>> Ryan J. Salva | Principal PM Manager Visual Studio Tools for >>>>> Apache Cordova rsa...@microsoft.com >>>>> 425 706 5270 office >>>>> 206 612 5079 mobile >>>>> >>>>> -Original Message- >>>>> From: Carlos Santana [mailto:csantan...@gmail.com] >>>>> Sent: Friday, April 15, 2016 5:47 PM >>>>> To: dev@cordova.apache.org >>>>> Subject: Re: Apache Con NA May 11-13 in Vancouver, BC >>>>> >>>>> No one from IBM MobileFirst going we don't have travel budget :-( >>>>> >>>>> A Cordova Face 2 Face might be useful and there might be a better >>>>> chance to get approval than Apache Con, also we stop doing the >>>>> Monthly Hangouts >>>> I >>>>> think they we're useful and community builder. >>>>> >>>>> - Carlos >>>>> @csantanapr >>>>> >>>>>> On Apr 15, 2016, at 4:13 PM, Simon MacDonald < >>>> simon.macdon...@gmail.com> >>>>> wrote: >>>>>> >>>>>> I decided not to go as ApacheCon is sandwiched between two other >>>>>> trips I need to make in May. >>>>>> >>>>>> That being said it would be nice to get another Cordova Face 2 >>>>>> Face sometime in the next few months. >>>>>> >>>>>> Simon Mac Donald >>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi >>>>>> .im% >>>>>> 2fsimonmacdonald&data=01%7c01%7crsalva%40microsoft.com%7c8e6fb728c >>>>>> 7b34 >>>>>> 8a9bc9908d365776f95%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=W >>>>>> oSAD 1sazA7ZjJBS8Xp8GznZi4nfnvua8peua88n3xA%3d >>>>>> >>>>>>> On Fri, Apr 15, 2016 at 3:35 PM, Steven Gill >>>>>>> >>>>> wrote: >>>>>>> >>>>>>> Hey Tony, >>
Re: [DISCUSS] Faster incremental builds
The only thing to watch out is folks modified files during after_prepare event, then they will be broken if the file have not changed and they modified/add content to the file a second time. To make this work the hook event will need to inform batch/node and plugins hooks on before_prepare and after_prepare the list of files that are going to be copy, so the hook owner can know not to modified the file if their file is not I the list. One real use case is Ionic and I think MobileFirst. For MobileForst I think we don't modified I think we just recreate new file ok every prepare For Ionic they edit the index.html to a class to to the body element to for platform identification - Carlos @csantanapr > On Apr 21, 2016, at 5:12 PM, Jason Ginchereau wrote: > > If "cordova clean" would also take care of deleting the files copied by > prepare, then I'd be confident in making prepare incremental by default. Then > if anyone was ever concerned about whether the incremental prepare was doing > the right thing, "cordova clean" would be a fairly obvious way to reset the > build. I still can't think of a realistic developer scenario where that would > be necessary, but it seems like the right thing for a "clean" command to do > regardless. > > So I will work on enhancing the "clean" function for each platform at the > same time I enable the incremental prepare. > > Jason > > -Original Message- > From: Jason Ginchereau [mailto:jason...@microsoft.com] > Sent: Wednesday, April 20, 2016 10:00 AM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Faster incremental builds > > My concern with making this the default behavior is that Cordova prepare > doesn't have a corresponding "clean" operation. While there is a "cordova > clean" command, it only does a clean for the native-code project (e.g. gradle > clean), which doesn't affect the files copied during prepare. I guess this > would only be a problem if you did something to give your source files older > last-modified times... then a cordova prepare/build/run that was incremental > would not pick up the older files, and "cordova clean" wouldn't fix it. I was > thinking a git checkout could do that, but upon investigation it actually > doesn't reset files' last-modified times. (I guess any source control tools > shouldn't, as it would mess up any kind of incremental build system.) > > Maybe "cordova clean" should also delete the files that are copied by > prepare? Or maybe there could be something like a "cordova prepare --force" > flag for the rare case when a non-incremental prepare is needed? Between > those two I'd prefer making "cordova clean" more thorough; I didn't think of > that until now. > > Jason > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Wednesday, April 20, 2016 9:18 AM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Faster incremental builds > > Thanks for sharing the stats! Looks like a great improvement! > > I'm fine with this going in sans flag if we test it bit more first. > > Have your tried it with the --browserify flag? >> On Apr 20, 2016 7:18 AM, "Victor Sosa" wrote: >> >> This is an amazing improvement in Cordova performance. Thanks Jason >> +1!! >> >>> On Wed, Apr 20, 2016 at 9:14 AM Shazron wrote: >>> >>> +1 what Jesse said >>> On Tuesday, April 19, 2016, Jesse wrote: This sounds great! Personally, I don't think this belongs behind a flag, why would anyone >>> not want to build faster? I think we just need to test more to make sure it functions as expected everywhere, and then it should just make it's way in directly, without >>> the overhead of addition flag code, or documentation ... @purplecabbage risingj.com On Tue, Apr 19, 2016 at 5:58 PM, Jason Ginchereau < >>> jason...@microsoft.com > wrote: > I collected data for 4 projects with varying numbers and sizes > of >>> source > files (mostly .js and .png): >Tiny : 17 files, 0.24 MB (A new Cordova project created from >>> the > VS template) >Small : 55 files, 7.7 MB >Medium:242 files, 44 MB >Large : 12,923 files, 134 MB > > Following are full -> incremental times for 'cordova prepare android' > commands, without any source file changes in between, averaged > over 5 warm > runs on my medium-spec Windows desktop machine with SSD: > >Tiny : 1.98 -> 1.84 s >Small : 2.40 -> 1.94 s >Medium: 4.22 -> 2.02 s >Large : 50.24 -> 5.81 s > > As you can see, larger projects see greatly improved prepare > times >> when > using the incremental option. > > Also, I confirmed that without using the --incremental option > with >> this > change, times are not measurably different compared to the > released version > 6.1
Re: Apache Con NA May 11-13 in Vancouver, BC
No one from IBM MobileFirst going we don't have travel budget :-( A Cordova Face 2 Face might be useful and there might be a better chance to get approval than Apache Con, also we stop doing the Monthly Hangouts I think they we're useful and community builder. - Carlos @csantanapr > On Apr 15, 2016, at 4:13 PM, Simon MacDonald > wrote: > > I decided not to go as ApacheCon is sandwiched between two other trips I > need to make in May. > > That being said it would be nice to get another Cordova Face 2 Face > sometime in the next few months. > > Simon Mac Donald > http://hi.im/simonmacdonald > >> On Fri, Apr 15, 2016 at 3:35 PM, Steven Gill wrote: >> >> Hey Tony, >> >> Due to the lack of committer response and the upcoming PGDAY EU event, I >> ended up not submitting a talk. I don't believe anyone from the Adobe >> Cordova team is going. >> >> >> >>> On Fri, Apr 15, 2016 at 6:21 AM, Homer, Tony wrote: >>> >>> I haven't seen any discussion about this lately - is anyone going? >>> I think I'm going to go and I need to book my travel today. >>> >>> I was in Austin at the same time as ApacheCon and dropped in to meet up >>> with some of you but I wasn't an attendee. >>> How is the conference itself? >>> >>> This year there is one Cordova session on the schedule (Advanced Apache >>> Cordova - Hazem Saleh, IBM[1]). >>> It would be nice to meet up again this year. >>> >>> [1] >> http://apachecon2016.sched.org/event/6OIr/advanced-apache-cordova-hazem-saleh-ibm >>> >>> Tony >>> >>> >>> >>> On 1/20/16, 1:48 AM, "Simon MacDonald" >>> wrote: >>> Yup, that was exactly what I was thinking. Check in see if we've made progress on what we talked about last time. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Jan 19, 2016 at 10:05 PM, Parashuram N wrote: > Like another Cordova Face to Face ? It would be almost 6 months since >> we > had the last one. > > -Original Message- > From: Simon MacDonald [mailto:simon.macdon...@gmail.com] > Sent: Tuesday, January 19, 2016 6:02 PM > To: dev@cordova.apache.org > Subject: Re: Apache Con NA May 11-13 in Vancouver, BC > > I would be interested in going as well. Might be an easier sell if we > could schedule a Cordova check up around the same time. > > Simon Mac Donald >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi.im%2fsimonmacdonald&data=01%7c01%7cpanarasi%40microsoft.com%7c2adb8eb8acd348e2632108d3213dc71f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=OSg6OMGtiPCppvOA4TuM5hv%2fjkfa8mqcyk1WqT8VSn4%3d > > On Tue, Jan 19, 2016 at 4:20 PM, Anis KADRI >>> wrote: > >> I'd be down to go. I went last year and our project had a few talks >> but still was super under represented so everyone that can make it >> should go I think. >> >> On Tue, Jan 19, 2016 at 11:49 AM Steven Gill < >> stevengil...@gmail.com> >> wrote: >> >>> I'm planning on going but it seems i'm the only one so far. >>> >>> On Tue, Jan 19, 2016 at 11:23 AM, Joe Bowser > wrote: >>> As usual, I'm not going to be attending this conference. I'm pretty >> sure I'm banned from attending this. On Tue, Jan 19, 2016 at 11:16 AM, Ryan J. Salva wrote: > If we can get critical mass among other committers, I'd love >> to > head >> up to > Vancouver for a few days. Without other Cordova committers > attending, >>> I'm > not sure I could justify attending solo. > > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Tuesday, January 19, 2016 11:05 AM > To: dev@cordova.apache.org > Subject: Apache Con NA May 11-13 in Vancouver, BC > > Anyone planning on submitting a talk for apachecon? > > The folks over at Apache Flex are wondering if we want to > partner to create a client-side track. >>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fevents >> .linuxfoundation.org >>> %2fevents%2fapachecon-north-america&data=01%7c01%7 >> crsalva%40microsoft.com >>> %7ca77249e9c394412deb6908d32103904c%7c72f988bf8 >> 6f141af91ab2d7cd011db47%7c1&sdata=DtyHuN1e3o5ARFZ5lNSvHlk0JwrY2zp5hBnt >> bQGSkQY%3d > > - > 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-unsubs
Re: [DISCUSS] Plugins release
No objections, plugins owners could benefit of the new way to handle the android permissions with common plugin On Thu, Apr 14, 2016 at 8:23 PM Simon MacDonald wrote: > Nope, do it. > On Apr 14, 2016 14:09, "Steven Gill" wrote: > > > I'm going to start this today. Any objections? > > On Apr 8, 2016 12:40 PM, "julio cesar sanchez" > > wrote: > > > > > I can wait, and maybe fix some issues this weekend. > > > > > > > > > El viernes, 8 de abril de 2016, Simon MacDonald < > > simon.macdon...@gmail.com > > > > > > > escribiĆ³: > > > > > > > I'm currently waiting for a third party to verify an enhancement to > > > media. > > > > Anyone have a burning desire to release plugins now or can we wait a > > bit > > > > longer? > > > > > > > > > > > > Simon Mac Donald > > > > http://hi.im/simonmacdonald > > > > > > > > On Wed, Apr 6, 2016 at 12:23 PM, Simon MacDonald < > > > > simon.macdon...@gmail.com > > > > > wrote: > > > > > > > > > Yeah, it can wait. It's just something I would like to get in to > > reduce > > > > > code duplication. I'm also working on CB-10776 as well. > > > > > > > > > > Simon Mac Donald > > > > > http://hi.im/simonmacdonald > > > > > > > > > > On Wed, Apr 6, 2016 at 4:11 AM, julio cesar sanchez < > > > > > jcesarmob...@gmail.com > wrote: > > > > > > > > > >> At least this 3 have changes: > > > > >> > > > > >> cordova-plugin-inappbrowser > > > > >> cordova-plugin-statusbar > > > > >> cordova-plugin-dialogs > > > > >> > > > > >> If this can wait, I want to add a small change on dialogs plugin > > this > > > > >> afternoon. > > > > >> > > > > >> I have another change almost ready for the inappbrowser, but might > > > take > > > > a > > > > >> while, so I can add it for the next release. > > > > >> > > > > >> > > > > >> > > > > >> 2016-04-05 19:59 GMT+02:00 Simon MacDonald < > > simon.macdon...@gmail.com > > > > >: > > > > >> > > > > >> > Hey all, > > > > >> > > > > > >> > I'd like to start the ball rolling for a new plugin release. > I've > > > done > > > > >> the > > > > >> > necessary changes to remove the need to copy > PermissionHelper.java > > > > into > > > > >> > every new Cordova Android Plugin. Now these plugins depend on > > > > >> > cordova-plugin-compat to provide that class. > > > > >> > > > > > >> > It would mean new minor versions of: > > > > >> > > > > > >> >- cordova-plugin-camera > > > > >> >- cordova-plugin-contacts > > > > >> >- cordova-plugin-file > > > > >> >- cordova-plugin-geolocation > > > > >> >- cordova-plugin-media > > > > >> >- cordova-plugin-media-capture > > > > >> >- cordova-plugin-compat > > > > >> > > > > > >> > Check out the background as to why were are doing this in this > > > thread: > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > http://markmail.org/message/cmmxrxqftlktkccg#query:+page:1+mid:e6dooljwv2l6orig+state:results > > > > >> > > > > > >> > Are there any objections towards moving to a new plugin release? > > Are > > > > >> there > > > > >> > other plugins that need to be bumped? > > > > >> > > > > > >> > > > > > >> > Simon Mac Donald > > > > >> > http://hi.im/simonmacdonald > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > >
Re: Inclusion of Evothings Studio on https://cordova.apache.org/
I agree, it can be randomize when it becomes a problem or before if someone has some bandwidth - Carlos @csantanapr > On Apr 12, 2016, at 2:06 AM, Dmitry Blotsky wrote: > > IĆ¢ā¬ā¢ve merged the PR. The change will go live the next time anyone does a > website deployment. > > Kindly, > Dmitry > >> On Apr 11, 2016, at 4:20 PM, Shazron wrote: >> >> Layout wise, it could get ugly (thus the randomizer). IMO we can accept the >> PR, I don't think there is even a task in JIRA (nor consensus) that we >> should even do the randomizer (at least until it becomes a problem). >> >> On Mon, Apr 11, 2016 at 3:44 AM, julio cesar sanchez >> wrote: >> >>> So should we accept the PR now? or wait until we have the tool randomizing >>> ready? >>> >>> 2016-03-31 23:00 GMT+02:00 Ryan J. Salva : >>> >>>> +1 >>>> >>>> Sent via Ć°ÅøāĀ± >>>> >>>> >>>> >>>> >>>> On Thu, Mar 31, 2016 at 1:52 PM -0700, "Parashuram N" < >>>> panar...@microsoft.com<mailto:panar...@microsoft.com>> wrote: >>>> >>>> +1 Ć¢ā¬ā let us add the tool >>>> >>>>> On 3/31/16, 4:20 AM, "Carlos Santana" wrote: >>>>> >>>>> I checked the website and I think it's a good tool to add, Cordova Devs >>>>> will be happy to learn and start playing with IoT >>>>>> On Wed, Mar 30, 2016 at 8:33 PM Shazron wrote: >>>>>> >>>>>> I don't have opposition to it being in Tools if there is consensus. >>>>>> For randomization, right now it's all static and that's easy, but now >>>>>> we have to introduce *JavaScript* into the mix :^O >>>>>> >>>>>> On Wed, Mar 30, 2016 at 1:17 PM, Parashuram N >>> >>>>>> wrote: >>>>>>> Thanks Mikael for the information. Others on the list, with this >>>>>> information, do we think that we should include this in our listing. >>>> While >>>>>> I do understand that we have a max limit and would not want the home >>>> page >>>>>> to be a place where we list a million tools, an option could be to >>>> separate >>>>>> tools from frameworks, and list tools as they come in. My guess is >>> that >>>>>> there are not many tools. If there are, could we look at randomizing >>> the >>>>>> tools and displaying only enough so as to not mess up the asthetics of >>>> the >>>>>> page ? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On 3/30/16, 1:51 AM, "Mikael Kindborg" >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Evothings is a tool that speeds up the development of Cordova apps, >>>> and >>>>>>>> provides plugins and libraries for IoT-functionality, notably >>>> Bluetooth >>>>>> Low >>>>>>>> Energy (BLE). >>>>>>>> >>>>>>>> Evothings Workbench is a tool you run on your computer. Code files >>>> can be >>>>>>>> edited in any editor and when a file is updated the current app is >>>>>> reloaded >>>>>>>> on connected mobile devices. There are also debugging tools for >>>>>> evaluating >>>>>>>> code and logging data from connected phones. >>>>>>>> >>>>>>>> Evothings Viewer is a Cordova app that connects to the Workbench. It >>>> it >>>>>>>> used to run and live-reload apps. The Viewer comes preconfigured >>> with >>>> a >>>>>>>> bunch of Cordova plugins (e.g. BLE). You can also build your custom >>>>>> Viewer >>>>>>>> and add your own plugins. The Viewer and related plugins are all >>> open >>>>>>>> source. >>>>>>>> >>>>>>>> There is also support for connecting to the Workbench from any web >>>>>> browser >>>>>>>> or web view, that is, any Cordova app. You don't have to use the >>>> Viewer. >>>>>>>&
Re: [ANNOUNCE] cordova-ios 4.1.1 released
Yay ! +1 Edna great job getting this thru On Fri, Apr 8, 2016 at 12:07 AM Edna Y Morales wrote: > > > cordova-ios@4.1.1 is on NPM now: https://www.npmjs.com/package/cordova-ios > Check out blog post at > https://cordova.apache.org/announcements/2016/04/04/ios-4.1.1.html and > retweet https://twitter.com/apachecordova/status/718229585758986241 > > > Thanks, > Edna Morales >
Re: [Android] Library Project/AAR alternatives to current plugin situation
Does this aligns in a similar way as how phonegap is recommending for iOS on using Cocoapods [1] to embed the Cordova WebView into an existing iOS App? Looking only from a Native Android developer eyes this will be the approach I would like if I have a pure native android app and for some reason I want to add a Cordova webview to a portion of my App. [1]: http://docs.phonegap.com/develop/1-embed-webview/ios/#pods On Wed, Apr 6, 2016 at 5:52 PM Joe Bowser wrote: > Hey > > I recently looked at how native Android developers could use the current > Cordova code with their projects, and I've noticed that there's some major > problems with our current approach of just copying the Java classes into a > project, such as resources getting merged together, and other related > issues, so I created a project that instead uses the InAppBrowser source as > an Android Library instead of just code thrown over the wall. > > The main advantage of this approach is that we can now build the library as > an AAR and distribute the plugins and the platform using jcenter and > mavenCentral and allow more Android developers to be able to use Cordova in > their apps and make their apps more hybrid. > > Anyway, the example code is here. > > https://github.com/infil00p/Library-Dev-Project > > I used a Cordova application to demonstrate this, but I could have easily > used a vanilla Android project. Hopefully this also allows for certain > plugins like the InAppBrowser to be a lot more managable and will also > allow us to add more unit tests to our projects. > > Any thoughts on this approach versus our current one? >
Re: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests
Oh so it means you don't want to work on the code :-p On Tue, Apr 5, 2016 at 6:50 PM Simon MacDonald wrote: > Thanks, I put a watch on that. > > > Simon Mac Donald > http://hi.im/simonmacdonald > > On Tue, Apr 5, 2016 at 6:48 PM, Carlos Santana > wrote: > > > Simon, I was not able to find a JIRA, I created a new JIRA [1] to enhance > > plugin.xml to allow to add attributes > > > > [1]: https://issues.apache.org/jira/browse/CB-11023 > > > > > > On Wed, Mar 23, 2016 at 11:30 AM Simon MacDonald < > > simon.macdon...@gmail.com> > > wrote: > > > > > Seems like editing attributes in a config-file is a wanted enhancement. > > Do > > > we have a JIRA for it? > > > > > > > > > Simon Mac Donald > > > http://hi.im/simonmacdonald > > > > > > On Tue, Mar 22, 2016 at 5:09 PM, Carlos Santana > > > wrote: > > > > > > > I agree to enable config.xml to be able to set or override using > > > > config-file (i.e. any xml file including strings.xml) > > > > I also think that adding support in config.xml and plugin.xml to edit > > > > attributes is very helpful, this is exactly what we are doing for one > > of > > > > our plugin to add the attribute android:name for and it > > > was a > > > > pain, and I think we still have problems doing it from > > > > before_plugin_install hook, it would be easier from plugin.xml > > > > > > > > > > > > > > > > On Tue, Mar 22, 2016 at 10:55 AM julio cesar sanchez < > > > > jcesarmob...@gmail.com> > > > > wrote: > > > > > > > > > Yes, Simon, that's my opinion, and we should show the conficting > > values > > > > and > > > > > the id of the plugin with the conficting values so the user knows > he > > > has > > > > to > > > > > change the values on the config.xml or remove the plugin. > > > > > > > > > > But we still will have problems if the plugin uses a hook to write > > > values > > > > > instead of using the config-file tag > > > > > > > > > > 2016-03-22 15:11 GMT+01:00 Alexis Kofman >: > > > > > > > > > > > Maybe the configured values of the plugins are sometimes just > > default > > > > > > values that the user can override through the config.xml file. > > > > > > What about adding a flag indicating whether the value is > > overridable > > > ? > > > > > My 2 > > > > > > cents ... > > > > > > > > > > > > On Tue, Mar 22, 2016 at 3:02 PM, Simon MacDonald < > > > > > > simon.macdon...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > So for Android's case you are thinking the order of precedence > > > should > > > > > be: > > > > > > > > > > > > > > config.xml > > > > > > > plugin.xml > > > > > > > AndroidManifest.xml // created by the "cordova" cli > > > > > > > > > > > > > > Then if config.xml overrides something that one of the plugins > > > > depends > > > > > on > > > > > > > then the app won't build. I can actually get behind that > proposal > > > if > > > > > I'm > > > > > > > understanding you correctly. > > > > > > > > > > > > > > > > > > > > > Simon Mac Donald > > > > > > > http://hi.im/simonmacdonald > > > > > > > > > > > > > > On Tue, Mar 22, 2016 at 9:51 AM, julio cesar sanchez < > > > > > > > jcesarmob...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > > I think, if there is a conflict between config.xml and > > plugin.xml > > > > we > > > > > > > should > > > > > > > > not build. > > > > > > > > > > > > > > > > If we pick config.xml values, the plugins with conflicting > > values > > > > > might > > > > > > > not > > > > > > > > work, and if we pick the plugin.xml values, the app might not > > > w
Re: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests
Simon, I was not able to find a JIRA, I created a new JIRA [1] to enhance plugin.xml to allow to add attributes [1]: https://issues.apache.org/jira/browse/CB-11023 On Wed, Mar 23, 2016 at 11:30 AM Simon MacDonald wrote: > Seems like editing attributes in a config-file is a wanted enhancement. Do > we have a JIRA for it? > > > Simon Mac Donald > http://hi.im/simonmacdonald > > On Tue, Mar 22, 2016 at 5:09 PM, Carlos Santana > wrote: > > > I agree to enable config.xml to be able to set or override using > > config-file (i.e. any xml file including strings.xml) > > I also think that adding support in config.xml and plugin.xml to edit > > attributes is very helpful, this is exactly what we are doing for one of > > our plugin to add the attribute android:name for and it > was a > > pain, and I think we still have problems doing it from > > before_plugin_install hook, it would be easier from plugin.xml > > > > > > > > On Tue, Mar 22, 2016 at 10:55 AM julio cesar sanchez < > > jcesarmob...@gmail.com> > > wrote: > > > > > Yes, Simon, that's my opinion, and we should show the conficting values > > and > > > the id of the plugin with the conficting values so the user knows he > has > > to > > > change the values on the config.xml or remove the plugin. > > > > > > But we still will have problems if the plugin uses a hook to write > values > > > instead of using the config-file tag > > > > > > 2016-03-22 15:11 GMT+01:00 Alexis Kofman : > > > > > > > Maybe the configured values of the plugins are sometimes just default > > > > values that the user can override through the config.xml file. > > > > What about adding a flag indicating whether the value is overridable > ? > > > My 2 > > > > cents ... > > > > > > > > On Tue, Mar 22, 2016 at 3:02 PM, Simon MacDonald < > > > > simon.macdon...@gmail.com> > > > > wrote: > > > > > > > > > So for Android's case you are thinking the order of precedence > should > > > be: > > > > > > > > > > config.xml > > > > > plugin.xml > > > > > AndroidManifest.xml // created by the "cordova" cli > > > > > > > > > > Then if config.xml overrides something that one of the plugins > > depends > > > on > > > > > then the app won't build. I can actually get behind that proposal > if > > > I'm > > > > > understanding you correctly. > > > > > > > > > > > > > > > Simon Mac Donald > > > > > http://hi.im/simonmacdonald > > > > > > > > > > On Tue, Mar 22, 2016 at 9:51 AM, julio cesar sanchez < > > > > > jcesarmob...@gmail.com > > > > > > wrote: > > > > > > > > > > > I think, if there is a conflict between config.xml and plugin.xml > > we > > > > > should > > > > > > not build. > > > > > > > > > > > > If we pick config.xml values, the plugins with conflicting values > > > might > > > > > not > > > > > > work, and if we pick the plugin.xml values, the app might not > work > > > the > > > > > way > > > > > > the user wants. > > > > > > > > > > > > I think both options are bad, the user wants the plugin to work > and > > > to > > > > > get > > > > > > the values he manually added and both aren't possible if there > are > > > > > > conflicts. > > > > > > > > > > > > > > > > > > 2016-03-22 13:28 GMT+01:00 Simon MacDonald < > > > simon.macdon...@gmail.com > > > > >: > > > > > > > > > > > > > When it comes to the AndroidManifest if config.xml and > plugin.xml > > > > > > (possibly > > > > > > > multiple plugin.xml's) disagree on the value of an attribute: > > > > > > > > > > > > > > - if the value is a boolean then it should default to 'false'. > > For > > > > > > instance > > > > > > > if it is an attribute like supports small screens if one plugin > > > sets > > > > it > > > > > > to > > > > > >
Re: [DISCUSS] cordova-windows patch release
Update blog with CLI 6.1.1 instead of 6.1.0 - Carlos @csantanapr > On Apr 5, 2016, at 4:31 AM, Vladimir Kotikov (Akvelon) > wrote: > > Please review the blog post: https://github.com/apache/cordova-docs/pull/572 > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Monday, April 4, 2016 10:23 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] cordova-windows patch release > > bump > Do we have a ETA on this Vote? > >> On Thu, Mar 31, 2016 at 8:09 AM Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> >> The PR has been merged. I'm going to start Vote thread soon. >> - >> Best regards, Vladimir >> >> -Original Message- >> From: Carlos Santana [mailto:csantan...@gmail.com] >> Sent: Tuesday, March 29, 2016 10:33 PM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] cordova-windows patch release >> >> Can you merge and include CB-10927 [1] ? >> >> [1]: https://github.com/apache/cordova-windows/pull/163 >> >> >> >> On Tue, Mar 29, 2016 at 10:47 AM Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> >>> Hi all >>> >>> We'd like to do a cordova-windows patch release to fix the following >>> issues: >>> * CB-10845 Invalidate manifest cache in prepare (a4c673e3) >>> * CB-10714 Ignore case for --archs (49812d44) >>> * CB-10138 Adds missing plugin metadata to plugin_list module for >>> Windows (45e5bd13) >>> >>> The proposed version number for this release is 4.3.2 >>> >>> Does anyone have any reason to delay this release? Any other patches >>> I need to include into this release? >>> >>> - >>> Best regards, Vladimir >>> >>> >>> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >>> For additional commands, e-mail: dev-h...@cordova.apache.org > ĆĀ¢ĆĆĀ„FĆ²VƧ7V'67&ā&RĆRĆĆāĆĀ¢FWbĆVƧ7V'67&ā&T6Ć·&FĆ·fƦ6ā RƦƷ&pĆĀ¤fĆ·"FFāFāƶƦĆ6ƶĆĆƦG2ĆRĆĆāĆĀ¢FWbĆā VĆ6Ć·&FĆ·fƦ6ā RƦƷ&pĆ - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [ANNOUNCE] Tools release
Great !, Thanks a lot Vladimir - Carlos @csantanapr > On Apr 5, 2016, at 2:23 AM, Vladimir Kotikov (Akvelon) > wrote: > > Blog: http://cordova.apache.org/news/2016/04/04/tools-release.html > Tweet: https://twitter.com/apachecordova/status/71718881055602 > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Monday, April 4, 2016 12:05 PM > To: dev@cordova.apache.org > Subject: [ANNOUNCE] Tools release > > Cordova-cli@6.1.1 & Plugman@1.2.1 has been released! > Check out > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.npmjs.com%2fpackage%2fcordova&data=01%7c01%7cv-vlkoti%40microsoft.com%7cee563827c0b6496e14a608d35c68442b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=6DC0uqzAgg1I0WgEJuJqX1aCHUK1c9%2fIIYbJMxja5Jg%3d > and > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.npmjs.com%2fpackage%2fplugman&data=01%7c01%7cv-vlkoti%40microsoft.com%7cee563827c0b6496e14a608d35c68442b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=y0t2A51KR7vUcOkWgCx%2bIwQEUlpVH74An5llYMrxPX0%3d > > - > Best regards, Vladimir > > - > 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: [DISCUSS] cordova-windows patch release
bump Do we have a ETA on this Vote? On Thu, Mar 31, 2016 at 8:09 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > The PR has been merged. I'm going to start Vote thread soon. > - > Best regards, Vladimir > > -Original Message----- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Tuesday, March 29, 2016 10:33 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] cordova-windows patch release > > Can you merge and include CB-10927 [1] ? > > [1]: https://github.com/apache/cordova-windows/pull/163 > > > > On Tue, Mar 29, 2016 at 10:47 AM Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > > > Hi all > > > > We'd like to do a cordova-windows patch release to fix the following > > issues: > > * CB-10845 Invalidate manifest cache in prepare (a4c673e3) > > * CB-10714 Ignore case for --archs (49812d44) > > * CB-10138 Adds missing plugin metadata to plugin_list module for > > Windows (45e5bd13) > > > > The proposed version number for this release is 4.3.2 > > > > Does anyone have any reason to delay this release? Any other patches I > > need to include into this release? > > > > - > > Best regards, Vladimir > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
LGTM - Carlos @csantanapr > On Apr 4, 2016, at 5:09 AM, Vladimir Kotikov (Akvelon) > wrote: > > The permanent release tags have been set and the packages have been published > to npm. > > Could someone please review announcement blog post at > https://github.com/apache/cordova-docs/pull/570 > > - > Best regards, Vladimir > > -----Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Friday, April 1, 2016 4:39 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > can we close the vote and release? > >> On Fri, Apr 1, 2016 at 9:38 AM Carlos Santana wrote: >> >> bump >> >> On Thu, Mar 31, 2016 at 1:27 PM Carlos Santana >> wrote: >> >>> +1 >>> >>> - Carlos >>> @csantanapr >>> >>>>> On Mar 31, 2016, at 1:17 PM, Vladimir Kotikov (Akvelon) < >>>> v-vlk...@microsoft.com> wrote: >>>> >>>> Just cherry-picked releasenotes to master >>>> - >>>> Best regards, Vladimir >>>> >>>> -Original Message- >>>> From: Carlos Santana [mailto:csantan...@gmail.com] >>>> Sent: Thursday, March 31, 2016 6:09 PM >>>> To: dev@cordova.apache.org >>>> Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 >>>> >>>> Burned again by not using --tags to fresh :-( >>>> >>>> But still cordova-cli master/HEAD is behind 3 commits need to be >>> updated, it's missing the >>> https://na01.safelinks.protection.outlook.com/?url=RELEASENOTES.md&da >>> ta=01%7c01%7cv-vlkoti%40microsoft.com%7c4d492fd59cd945deab3b08d359767 >>> d19%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mAKpEs1VeHtDgr6DinoF >>> QjrSX3WZblU3IpZAh8LHbEY%3d >>> changes for 6.1.1 >>>> >>>> >>>> >>>>> On Thu, Mar 31, 2016 at 3:36 AM Vladimir Kotikov (Akvelon) < >>> v-vlk...@microsoft.com> wrote: >>>>> >>>>> Carlos, >>>>> I was able to verify tags for lib and cli: >>>>> >>>>> coho verify-tags >>>>> Running from d:\cordova >>>>> Paste in print-tags output then hit Enter >>>>> cordova-lib: 6.1.1 (107e273647) >>>>> cordova-plugman: 1.2.1 (f05a7ef8cf) >>>>> cordova-cli: 6.1.1 (8e730ac376) >>>>> >>>>> cordova-lib: Tag hash verified. >>>>> cordova-plugman: Tag hash verified. >>>>> cordova-cli: Tag hash verified. >>>>> >>>>> Looks like you just need to run `git fetch origin --tags` to >>>>> update the tags in your local repo. They had been moved since last >>>>> release attempt. I should have notify about this when started the vote. >>>>> >>>>> - >>>>> Best regards, Vladimir >>>>> >>>>> -Original Message- >>>>> From: Carlos Santana [mailto:csantan...@gmail.com] >>>>> Sent: Tuesday, March 29, 2016 2:35 PM >>>>> To: dev@cordova.apache.org >>>>> Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 >>>>> >>>>> I agree, we can discuss later the release for cordova-commons >>>>> >>>>> - Carlos >>>>> @csantanapr >>>>> >>>>>>> On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) < >>>>>> v-vlk...@microsoft.com> wrote: >>>>>> >>>>>> Carlos, I've reviewed and merged these PRs. However the only two >>>>>> PRs >>>>> that need to be included into this release are #415 [1] and #416 [2]. >>>>> The other two are for cordova-common and I guess we have nothing >>>>> to do with them for now. >>>>>> >>>>>> Summarizing, the release notes for 6.1.1 will look like this: >>>>>> >>>>>> ### 6.1.1 (Mar 29, 2016) >>>>>> * CB-10961 Error no such file or directory adding ios platform >>>>>> when >>>>> plugins present or required >>>>>> * CB-10908 Reload the config.xml before writing the saved plugin >>>>>> >>>>>> [1] https://github.com/apache/cordova-lib/pull/415 >>>>>> [2] https://github.com/apache/cordova-lib/pull/416 >>>>>> >>>&g
Re: [DISCUSS] Core Plugins and Android API 23
Simon I like approach Can we move to this approach now? Yes Then once the downstream distro's support API 23 and the new API methods in CordovaInterface we can move this into Cordova Android proper? Yes +1 On Thu, Mar 31, 2016 at 6:38 PM Joe Bowser wrote: > LGTM! > > On Thu, Mar 31, 2016 at 3:02 PM, Simon MacDonald < > simon.macdon...@gmail.com> > wrote: > > > I really hate the fact we need to add that PermissionHelper.java file to > > each and every plugin that requires API 23 permission support. Especially > > since the package the class is in is different for each plugin so we can > > two, three or more copies of the same code in an app. That's just > wasteful. > > > > Joe responded to my bitching by saying "Maybe we should create a > > permissions plugin for this and make everything go through that" which > set > > my mind a racing (perhaps I was just over caffeinated) and I decided to > > prototype it this afternoon. > > > > I've created a new plugin called cordova-plugin-compat over at > > https://github.com/macdonst/cordova-plugin-compat and all it does is > > deliver the org.apache.cordova.PermissionHelper class. I then turned > around > > and removed the class from the camera plugin and make > cordova-plugin-camera > > depend on cordova-plugin-compat. > > > > You can see that change over on my camera fork: > > > > https://github.com/macdonst > > /cordova-plugin-camera/commit/58b72cb5c3109481df9f337ad97607858681b37e > > > > Can we move to this approach now? Then once the downstream distro's > support > > API 23 and the new API methods in CordovaInterface we can move this into > > Cordova Android proper? > > > > Thoughts? Are there use cases this approach doesn't work for? > > > > > > Simon Mac Donald > > http://hi.im/simonmacdonald > > > > On Fri, Feb 5, 2016 at 2:32 PM, Richard Knoll > > wrote: > > > > > Yep, I left it out of the first round by mistake; I was looking at an > out > > > of date version of cordova-plugin-media at the time. I've got a PR open > > > that adds the helper here: > > > > > > https://github.com/apache/cordova-plugin-media/pull/79 > > > > > > Thanks, > > > Richard > > > > > > -Original Message- > > > From: julio cesar sanchez [mailto:jcesarmob...@gmail.com] > > > Sent: Friday, February 5, 2016 7:20 AM > > > To: dev@cordova.apache.org > > > Subject: Re: [DISCUSS] Core Plugins and Android API 23 > > > > > > Yeah, that one. > > > > > > > > > El viernes, 5 de febrero de 2016, Homer, Tony > > > escribiĆ³: > > > > > > > It took me a while to find it, but I guess you mean CB-10455? > > > > > > > > > > > > > > > > On 2/5/16, 7:56 AM, "julio cesar sanchez" > > > > wrote: > > > > > > > > >I think we just forgot, somebody mentioned this on slack and there > is > > > > >an issue open on JIRA. > > > > > > > > > >2016-02-05 13:52 GMT+01:00 Homer, Tony > > > >: > > > > > > > > > >> Earlier in this thread, Richard stated: > > > > >> >> This change has been merged into the file, camera, geolocation, > > > > >> >> and > > > > >> contacts plugins (media did not actually require any change). > > > > >> > > > > >> > > > > >> Media was updated on 1/15 but it still has a "cordova-android > > > > >=5.0.0-dev" > > > > >> engine tag. > > > > >> I couldn't find any other discussion about this on the list and > > > > >> wondered why it was retained for media. > > > > >> Was this an oversight? > > > > >> > > > > >> > > > > >> Thanks! > > > > >> Tony > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> On 1/15/16, 4:40 PM, "Simon MacDonald" > > > > wrote: > > > > >> > > > > >> >LGTM > > > > >> > > > > > >> >+1 > > > > >> > > > > > >> >Simon Mac Donald > > > > >> > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fhi > > > > >> > >.im%2fsim
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
can we close the vote and release? On Fri, Apr 1, 2016 at 9:38 AM Carlos Santana wrote: > bump > > On Thu, Mar 31, 2016 at 1:27 PM Carlos Santana > wrote: > >> +1 >> >> - Carlos >> @csantanapr >> >> > On Mar 31, 2016, at 1:17 PM, Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> > >> > Just cherry-picked releasenotes to master >> > - >> > Best regards, Vladimir >> > >> > -Original Message- >> > From: Carlos Santana [mailto:csantan...@gmail.com] >> > Sent: Thursday, March 31, 2016 6:09 PM >> > To: dev@cordova.apache.org >> > Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 >> > >> > Burned again by not using --tags to fresh :-( >> > >> > But still cordova-cli master/HEAD is behind 3 commits need to be >> updated, it's missing the >> https://na01.safelinks.protection.outlook.com/?url=RELEASENOTES.md&data=01%7c01%7cv-vlkoti%40microsoft.com%7c4d492fd59cd945deab3b08d359767d19%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mAKpEs1VeHtDgr6DinoFQjrSX3WZblU3IpZAh8LHbEY%3d >> changes for 6.1.1 >> > >> > >> > >> >> On Thu, Mar 31, 2016 at 3:36 AM Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> >> >> >> Carlos, >> >> I was able to verify tags for lib and cli: >> >> >> >> coho verify-tags >> >> Running from d:\cordova >> >> Paste in print-tags output then hit Enter >> >>cordova-lib: 6.1.1 (107e273647) >> >>cordova-plugman: 1.2.1 (f05a7ef8cf) >> >>cordova-cli: 6.1.1 (8e730ac376) >> >> >> >> cordova-lib: Tag hash verified. >> >> cordova-plugman: Tag hash verified. >> >> cordova-cli: Tag hash verified. >> >> >> >> Looks like you just need to run `git fetch origin --tags` to update >> >> the tags in your local repo. They had been moved since last release >> >> attempt. I should have notify about this when started the vote. >> >> >> >> - >> >> Best regards, Vladimir >> >> >> >> -Original Message- >> >> From: Carlos Santana [mailto:csantan...@gmail.com] >> >> Sent: Tuesday, March 29, 2016 2:35 PM >> >> To: dev@cordova.apache.org >> >> Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 >> >> >> >> I agree, we can discuss later the release for cordova-commons >> >> >> >> - Carlos >> >> @csantanapr >> >> >> >>>> On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) < >> >>> v-vlk...@microsoft.com> wrote: >> >>> >> >>> Carlos, I've reviewed and merged these PRs. However the only two PRs >> >> that need to be included into this release are #415 [1] and #416 [2]. >> >> The other two are for cordova-common and I guess we have nothing to do >> >> with them for now. >> >>> >> >>> Summarizing, the release notes for 6.1.1 will look like this: >> >>> >> >>> ### 6.1.1 (Mar 29, 2016) >> >>> * CB-10961 Error no such file or directory adding ios platform when >> >> plugins present or required >> >>> * CB-10908 Reload the config.xml before writing the saved plugin >> >>> >> >>> [1] https://github.com/apache/cordova-lib/pull/415 >> >>> [2] https://github.com/apache/cordova-lib/pull/416 >> >>> >> >>> - >> >>> Best regards, Vladimir >> >>> >> >>> -Original Message- >> >>> From: Carlos Santana [mailto:csantan...@gmail.com] >> >>> Sent: Monday, March 28, 2016 10:50 PM >> >>> To: dev@cordova.apache.org >> >>> Subject: [DISCUSS] Tools Release CLI/LIB 6.1.1 >> >>> >> >>> I would like to see a patch release for the tools >> >>> >> >>> Interested if someone can review and merge these PRs and get include >> >>> it >> >> in the release: >> >>> >> >>> https://github.com/apache/cordova-lib/pull/418 >> >>> https://github.com/apache/cordova-lib/pull/417 >> >>> https://github.com/apache/cordova-lib/pull/416 >> >>> https://github.com/apache/cordova-lib/pull/415 >> >>> >> >>> >> >>> - 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 >> > >> ĆĀ¢ĆĆĀ„FĆ² >> VƧ7V'67&ā&RĆ RĆĆ āĆĀ¢ FWbĆVƧ7V'67&ā&T 6Ć·&FĆ·f Ʀ 6ā RƦƷ&pĆĀ¤fĆ·" FFāFāƶƦ Ć >> 6ƶĆĆ Ć¦G2Ć RĆĆ āĆĀ¢ FWbĆā VĆ 6Ć·&FĆ·f Ʀ 6ā RƦƷ&pĆ >> >
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
bump On Thu, Mar 31, 2016 at 1:27 PM Carlos Santana wrote: > +1 > > - Carlos > @csantanapr > > > On Mar 31, 2016, at 1:17 PM, Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > > > > Just cherry-picked releasenotes to master > > - > > Best regards, Vladimir > > > > -Original Message- > > From: Carlos Santana [mailto:csantan...@gmail.com] > > Sent: Thursday, March 31, 2016 6:09 PM > > To: dev@cordova.apache.org > > Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > > > Burned again by not using --tags to fresh :-( > > > > But still cordova-cli master/HEAD is behind 3 commits need to be > updated, it's missing the > https://na01.safelinks.protection.outlook.com/?url=RELEASENOTES.md&data=01%7c01%7cv-vlkoti%40microsoft.com%7c4d492fd59cd945deab3b08d359767d19%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mAKpEs1VeHtDgr6DinoFQjrSX3WZblU3IpZAh8LHbEY%3d > changes for 6.1.1 > > > > > > > >> On Thu, Mar 31, 2016 at 3:36 AM Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > >> > >> Carlos, > >> I was able to verify tags for lib and cli: > >> > >> coho verify-tags > >> Running from d:\cordova > >> Paste in print-tags output then hit Enter > >>cordova-lib: 6.1.1 (107e273647) > >>cordova-plugman: 1.2.1 (f05a7ef8cf) > >>cordova-cli: 6.1.1 (8e730ac376) > >> > >> cordova-lib: Tag hash verified. > >> cordova-plugman: Tag hash verified. > >> cordova-cli: Tag hash verified. > >> > >> Looks like you just need to run `git fetch origin --tags` to update > >> the tags in your local repo. They had been moved since last release > >> attempt. I should have notify about this when started the vote. > >> > >> - > >> Best regards, Vladimir > >> > >> -Original Message- > >> From: Carlos Santana [mailto:csantan...@gmail.com] > >> Sent: Tuesday, March 29, 2016 2:35 PM > >> To: dev@cordova.apache.org > >> Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 > >> > >> I agree, we can discuss later the release for cordova-commons > >> > >> - Carlos > >> @csantanapr > >> > >>>> On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) < > >>> v-vlk...@microsoft.com> wrote: > >>> > >>> Carlos, I've reviewed and merged these PRs. However the only two PRs > >> that need to be included into this release are #415 [1] and #416 [2]. > >> The other two are for cordova-common and I guess we have nothing to do > >> with them for now. > >>> > >>> Summarizing, the release notes for 6.1.1 will look like this: > >>> > >>> ### 6.1.1 (Mar 29, 2016) > >>> * CB-10961 Error no such file or directory adding ios platform when > >> plugins present or required > >>> * CB-10908 Reload the config.xml before writing the saved plugin > >>> > >>> [1] https://github.com/apache/cordova-lib/pull/415 > >>> [2] https://github.com/apache/cordova-lib/pull/416 > >>> > >>> - > >>> Best regards, Vladimir > >>> > >>> -Original Message- > >>> From: Carlos Santana [mailto:csantan...@gmail.com] > >>> Sent: Monday, March 28, 2016 10:50 PM > >>> To: dev@cordova.apache.org > >>> Subject: [DISCUSS] Tools Release CLI/LIB 6.1.1 > >>> > >>> I would like to see a patch release for the tools > >>> > >>> Interested if someone can review and merge these PRs and get include > >>> it > >> in the release: > >>> > >>> https://github.com/apache/cordova-lib/pull/418 > >>> https://github.com/apache/cordova-lib/pull/417 > >>> https://github.com/apache/cordova-lib/pull/416 > >>> https://github.com/apache/cordova-lib/pull/415 > >>> > >>> > >>> - 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 > > > ĆĀ¢ĆĆĀ„FĆ² > VƧ7V'67&ā&RĆ RĆĆ āĆĀ¢ FWbĆVƧ7V'67&ā&T 6Ć·&FĆ·f Ʀ 6ā RƦƷ&pĆĀ¤fĆ·" FFāFāƶƦ Ć > 6ƶĆĆ Ć¦G2Ć RĆĆ āĆĀ¢ FWbĆā VĆ 6Ć·&FĆ·f Ʀ 6ā RƦƷ&pĆ >
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
+1 - Carlos @csantanapr > On Mar 31, 2016, at 1:17 PM, Vladimir Kotikov (Akvelon) > wrote: > > Just cherry-picked releasenotes to master > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Thursday, March 31, 2016 6:09 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > Burned again by not using --tags to fresh :-( > > But still cordova-cli master/HEAD is behind 3 commits need to be updated, > it's missing the > https://na01.safelinks.protection.outlook.com/?url=RELEASENOTES.md&data=01%7c01%7cv-vlkoti%40microsoft.com%7c4d492fd59cd945deab3b08d359767d19%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mAKpEs1VeHtDgr6DinoFQjrSX3WZblU3IpZAh8LHbEY%3d > changes for 6.1.1 > > > >> On Thu, Mar 31, 2016 at 3:36 AM Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> >> Carlos, >> I was able to verify tags for lib and cli: >> >> coho verify-tags >> Running from d:\cordova >> Paste in print-tags output then hit Enter >>cordova-lib: 6.1.1 (107e273647) >>cordova-plugman: 1.2.1 (f05a7ef8cf) >>cordova-cli: 6.1.1 (8e730ac376) >> >> cordova-lib: Tag hash verified. >> cordova-plugman: Tag hash verified. >> cordova-cli: Tag hash verified. >> >> Looks like you just need to run `git fetch origin --tags` to update >> the tags in your local repo. They had been moved since last release >> attempt. I should have notify about this when started the vote. >> >> - >> Best regards, Vladimir >> >> -Original Message- >> From: Carlos Santana [mailto:csantan...@gmail.com] >> Sent: Tuesday, March 29, 2016 2:35 PM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 >> >> I agree, we can discuss later the release for cordova-commons >> >> - Carlos >> @csantanapr >> >>>> On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) < >>> v-vlk...@microsoft.com> wrote: >>> >>> Carlos, I've reviewed and merged these PRs. However the only two PRs >> that need to be included into this release are #415 [1] and #416 [2]. >> The other two are for cordova-common and I guess we have nothing to do >> with them for now. >>> >>> Summarizing, the release notes for 6.1.1 will look like this: >>> >>> ### 6.1.1 (Mar 29, 2016) >>> * CB-10961 Error no such file or directory adding ios platform when >> plugins present or required >>> * CB-10908 Reload the config.xml before writing the saved plugin >>> >>> [1] https://github.com/apache/cordova-lib/pull/415 >>> [2] https://github.com/apache/cordova-lib/pull/416 >>> >>> - >>> Best regards, Vladimir >>> >>> -Original Message- >>> From: Carlos Santana [mailto:csantan...@gmail.com] >>> Sent: Monday, March 28, 2016 10:50 PM >>> To: dev@cordova.apache.org >>> Subject: [DISCUSS] Tools Release CLI/LIB 6.1.1 >>> >>> I would like to see a patch release for the tools >>> >>> Interested if someone can review and merge these PRs and get include >>> it >> in the release: >>> >>> https://github.com/apache/cordova-lib/pull/418 >>> https://github.com/apache/cordova-lib/pull/417 >>> https://github.com/apache/cordova-lib/pull/416 >>> https://github.com/apache/cordova-lib/pull/415 >>> >>> >>> - 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 > ĆĀ¢ĆĆĀ„FĆ²VƧ7V'67&ā&RĆRĆĆāĆĀ¢FWbĆVƧ7V'67&ā&T6Ć·&FĆ·fƦ6ā RƦƷ&pĆĀ¤fĆ·"FFāFāƶƦĆ6ƶĆĆƦG2ĆRĆĆāĆĀ¢FWbĆā VĆ6Ć·&FĆ·fƦ6ā RƦƷ&pĆ - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE] Tools release attempt 2
oops I was able to verify the tags after doing git fetch origin --tags š $ coho verify-tags Running from ~/dev/cordova Paste in print-tags output then hit Enter cordova-lib: 6.1.1 (107e273647) cordova-plugman: 1.2.1 (f05a7ef8cf) cordova-cli: 6.1.1 (8e730ac376) cordova-lib: Tag hash verified. cordova-plugman: Tag hash verified. cordova-cli: Tag hash verified. On Thu, Mar 31, 2016 at 7:51 AM Edna Y Morales wrote: > I vote +1 > > -Verified tags for all 3 tools with coho verify-tags > -Tested hello world app with ios and android and all core plugins installed > -Created hello world app with windows and all core plugins installed, but > did not run on device or emulator > > Thanks, > *Edna Morales* > > [image: Inactive hide details for Carlos Santana ---03/30/2016 06:10:27 > PM---I vote +1 coho verify-archive vote-6.1.1/cordova-6.1.1.tgz]Carlos > Santana ---03/30/2016 06:10:27 PM---I vote +1 coho verify-archive > vote-6.1.1/cordova-6.1.1.tgz > > From: Carlos Santana > To: "dev@cordova.apache.org" > Date: 03/30/2016 06:10 PM > Subject: Re: [VOTE] Tools release attempt 2 > -- > > > > > I vote +1 > > coho verify-archive vote-6.1.1/cordova-6.1.1.tgz > coho verify-archive vote-6.1.1/cordova-lib-6.1.1.tgz > coho verify-archive vote-6.1.1/plugman-1.2.1.tgz > > verify tag for cordova-plugman 6.1.1 > > was not able to verify tags for lib and cli, > no problem with release content and signatures, just the tags need to be > updated in the git repo > > cordova-cli tag 6.1.1 needs to be move to hash 8e730ac376 > cordova-lib tag 6.1.1 needs to be move to hash 107e273647 > > Also cordova-cli master doesn't have latest commits from 8e730ac376 > > Tested hello-world app with ios and android > > $ coho verify-tags > Running from /Users/csantana23/Documents/dev/cordova > Paste in print-tags output then hit Enter > cordova-lib: 6.1.1 (107e273647) > cordova-lib: Hashes don't match! > > $ coho verify-tags > Running from /Users/csantana23/Documents/dev/cordova > Paste in print-tags output then hit Enter > cordova-cli: 6.1.1 (8e730ac376) > cordova-cli: Hashes don't match! > > > > > On Tue, Mar 29, 2016 at 10:33 AM Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.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-10980 > > Both tools have been published to dist/dev: > > https://dist.apache.org/repos/dist/dev/cordova/CB-10980 > > > > The packages were published from their corresponding git tags: > > cordova-lib: 6.1.1 (107e273647) > > cordova-plugman: 1.2.1 (f05a7ef8cf) > > cordova-cli: 6.1.1 (8e730ac376) > > > > 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 > > * Ensured continuous build was green when repos were tagged > > * Created and ran mobilespec app on Android and Windows > > * Ran mobilespec app with --browserify flag on Android > > * Ensured unit tests are passing for cli, lib and plugman > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > >
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
Burned again by not using --tags to fresh :-( But still cordova-cli master/HEAD is behind 3 commits need to be updated, it's missing the RELEASENOTES.md changes for 6.1.1 On Thu, Mar 31, 2016 at 3:36 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Carlos, > I was able to verify tags for lib and cli: > > coho verify-tags > Running from d:\cordova > Paste in print-tags output then hit Enter > cordova-lib: 6.1.1 (107e273647) > cordova-plugman: 1.2.1 (f05a7ef8cf) > cordova-cli: 6.1.1 (8e730ac376) > > cordova-lib: Tag hash verified. > cordova-plugman: Tag hash verified. > cordova-cli: Tag hash verified. > > Looks like you just need to run `git fetch origin --tags` to update the > tags in your local repo. They had been moved since last release attempt. I > should have notify about this when started the vote. > > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Tuesday, March 29, 2016 2:35 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > I agree, we can discuss later the release for cordova-commons > > - Carlos > @csantanapr > > > On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > > > > Carlos, I've reviewed and merged these PRs. However the only two PRs > that need to be included into this release are #415 [1] and #416 [2]. The > other two are for cordova-common and I guess we have nothing to do with > them for now. > > > > Summarizing, the release notes for 6.1.1 will look like this: > > > > ### 6.1.1 (Mar 29, 2016) > > * CB-10961 Error no such file or directory adding ios platform when > plugins present or required > > * CB-10908 Reload the config.xml before writing the saved plugin > > > > [1] https://github.com/apache/cordova-lib/pull/415 > > [2] https://github.com/apache/cordova-lib/pull/416 > > > > - > > Best regards, Vladimir > > > > -Original Message- > > From: Carlos Santana [mailto:csantan...@gmail.com] > > Sent: Monday, March 28, 2016 10:50 PM > > To: dev@cordova.apache.org > > Subject: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > > > I would like to see a patch release for the tools > > > > Interested if someone can review and merge these PRs and get include it > in the release: > > > > https://github.com/apache/cordova-lib/pull/418 > > https://github.com/apache/cordova-lib/pull/417 > > https://github.com/apache/cordova-lib/pull/416 > > https://github.com/apache/cordova-lib/pull/415 > > > > - > > 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: Inclusion of Evothings Studio on https://cordova.apache.org/
I checked the website and I think it's a good tool to add, Cordova Devs will be happy to learn and start playing with IoT On Wed, Mar 30, 2016 at 8:33 PM Shazron wrote: > I don't have opposition to it being in Tools if there is consensus. > For randomization, right now it's all static and that's easy, but now > we have to introduce *JavaScript* into the mix :^O > > On Wed, Mar 30, 2016 at 1:17 PM, Parashuram N > wrote: > > Thanks Mikael for the information. Others on the list, with this > information, do we think that we should include this in our listing. While > I do understand that we have a max limit and would not want the home page > to be a place where we list a million tools, an option could be to separate > tools from frameworks, and list tools as they come in. My guess is that > there are not many tools. If there are, could we look at randomizing the > tools and displaying only enough so as to not mess up the asthetics of the > page ? > > > > > > > > > > On 3/30/16, 1:51 AM, "Mikael Kindborg" > wrote: > > > >>Hi, > >> > >>Evothings is a tool that speeds up the development of Cordova apps, and > >>provides plugins and libraries for IoT-functionality, notably Bluetooth > Low > >>Energy (BLE). > >> > >>Evothings Workbench is a tool you run on your computer. Code files can be > >>edited in any editor and when a file is updated the current app is > reloaded > >>on connected mobile devices. There are also debugging tools for > evaluating > >>code and logging data from connected phones. > >> > >>Evothings Viewer is a Cordova app that connects to the Workbench. It it > >>used to run and live-reload apps. The Viewer comes preconfigured with a > >>bunch of Cordova plugins (e.g. BLE). You can also build your custom > Viewer > >>and add your own plugins. The Viewer and related plugins are all open > >>source. > >> > >>There is also support for connecting to the Workbench from any web > browser > >>or web view, that is, any Cordova app. You don't have to use the Viewer. > >>The documentation for how to do this is currently being updated. > Basically > >>you just connect using this URL: > >> > >> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdeploy.evothings.com%2fconnect%2fCONNECT_KEY&data=01%7c01%7cpanarasi%40microsoft.com%7c88a1c4c02aa048583f3e08d358788ff5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iglzYysd7Eykhicg1TrwPdzTG3oRXmkeU2iEkjUoNOM%3d > >> > >>CONNECT_KEY is an 8 character code you get in the Workbench. > >> > >>Here is the documentation page specifically related to Cordova: > >> > >> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fevothings.com%2fdoc%2fstarter-guides%2fcordova-starter-guide.html&data=01%7c01%7cpanarasi%40microsoft.com%7c88a1c4c02aa048583f3e08d358788ff5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=u02xtdYUQU41nyiVOaJAF85GHlJEYPTBUpfMp9wCnIA%3d > >> > >>The file structure for an Evothings app is fully compatible with Cordova. > >>You can also take any Cordova app basically, and drag it into Evothings > >>Workbench and use live reload and debugging tools. > >> > >>To deploy an app built using Evothings Studio, you just build it with > >>Cordova, using the Cordova CLI. To help people building their native > apps, > >>we have documented how to install and use Cordova on the Evothings > >>documentation web site. > >> > >>Hope this summary helps! > >> > >>It is a good idea to clarify how Cordova is used in Evothings Studio in > the > >>pull request, will do this if the pull request is accepted. > >> > >>Any feedback you have on Evothings Studio is most welcome! > >> > >>Best regards, Mikael > >> > >>PS. Just to be clear, I work at Evothings and designed and implemented > the > >>live reload system used in Evothings Studio along with many parts of the > >>Workbench and the Viewer app. > >> > >> > >>On 30 March 2016 at 00:09, Parashuram N wrote: > >> > >>> Hey, > >>> > >>> While the discussion on including additional tools is still happening > on > >>> the mailing list, I had a quick question about the Evothings Studio. I > was > >>> looking at the website and it was not clear if the tool is based on > >>> Cordova/Phonegap. > >>> Is Evothiongs based on Cordova and are the device APIs based on Apache > >>> Cordova ? > >>> > >>> The purpose of the tooling showcase is to show off the various Cordova > >>> development tools, and it would be helpful if you could also tell us > how > >>> Cordova is used. Maybe we should add that as a part of the description > in > >>> the pull request ? > >>> > >>> -Original Message- > >>> From: Mikael Kindborg [mailto:mikael.kindb...@gmail.com] > >>> Sent: Thursday, March 24, 2016 2:15 AM > >>> To: dev@cordova.apache.org > >>> Subject: Inclusion of Evothings Studio on > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fcordova.apache.org%2f&data=01%7c01%7cpanarasi%40microsoft.com%7c88a1c4c02aa048583f3e08d358788ff5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=OLx8gOBhELyfi1ukS%2bjjtEBGiRS9rp1g
Re: [VOTE] Tools release attempt 2
I vote +1 coho verify-archive vote-6.1.1/cordova-6.1.1.tgz coho verify-archive vote-6.1.1/cordova-lib-6.1.1.tgz coho verify-archive vote-6.1.1/plugman-1.2.1.tgz verify tag for cordova-plugman 6.1.1 was not able to verify tags for lib and cli, no problem with release content and signatures, just the tags need to be updated in the git repo cordova-cli tag 6.1.1 needs to be move to hash 8e730ac376 cordova-lib tag 6.1.1 needs to be move to hash 107e273647 Also cordova-cli master doesn't have latest commits from 8e730ac376 Tested hello-world app with ios and android $ coho verify-tags Running from /Users/csantana23/Documents/dev/cordova Paste in print-tags output then hit Enter cordova-lib: 6.1.1 (107e273647) cordova-lib: Hashes don't match! $ coho verify-tags Running from /Users/csantana23/Documents/dev/cordova Paste in print-tags output then hit Enter cordova-cli: 6.1.1 (8e730ac376) cordova-cli: Hashes don't match! On Tue, Mar 29, 2016 at 10:33 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.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-10980 > Both tools have been published to dist/dev: > https://dist.apache.org/repos/dist/dev/cordova/CB-10980 > > The packages were published from their corresponding git tags: > cordova-lib: 6.1.1 (107e273647) > cordova-plugman: 1.2.1 (f05a7ef8cf) > cordova-cli: 6.1.1 (8e730ac376) > > 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 > * Ensured continuous build was green when repos were tagged > * Created and ran mobilespec app on Android and Windows > * Ran mobilespec app with --browserify flag on Android > * Ensured unit tests are passing for cli, lib and plugman > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [DISCUSS] cordova-windows patch release
Can you merge and include CB-10927 [1] ? [1]: https://github.com/apache/cordova-windows/pull/163 On Tue, Mar 29, 2016 at 10:47 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Hi all > > We'd like to do a cordova-windows patch release to fix the following > issues: > * CB-10845 Invalidate manifest cache in prepare (a4c673e3) > * CB-10714 Ignore case for --archs (49812d44) > * CB-10138 Adds missing plugin metadata to plugin_list module for > Windows (45e5bd13) > > The proposed version number for this release is 4.3.2 > > Does anyone have any reason to delay this release? Any other patches I > need to include into this release? > > - > Best regards, Vladimir > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: Adding Examples for Plugins in the ReadMe
"With great power comes great responsibilities" Adding this would require responsibilities of maintenance and up to date working examples backed up with CI. In other words it's good idea to add docs with more complex examples on how to use the plugin, some of them already are located in mobilespec and plugin test cases, which give us confident that scenario are in good shape. anything not already covered by CI would require to write test cases to make sure examples continue to work with plugin and platforms changes. I would not put the content in a 3rd party Git Repo if it's something that is part of the Apache Cordova project. Just request a INFRA ticket for git repo to be created. We can start with one like Jesse said "cordova-demos" or "cordova-examples" either one is fine On Tue, Mar 29, 2016 at 12:56 AM Robert Posener wrote: > Also... > These examples could be developed in such a way as to become part of the > Cordova automated testing that is performed before a new version release, > thereby adding more complex tests to the test suite. > You'll need to be careful of this anyway (ie, It would look pretty bad if > these examples were copied by a Cordova app developer exactly as shown and > then they didn't work). > > Regards > *Rob Posener* > 0419 012 627 > > On 29 March 2016 at 11:10, Parashuram N wrote: > > > Including a demo folder in each plugin is good. If it is checked in, we > > ensure that the example and the plugin use the same version of the API. > > However, there may be some examples (typically in the file plugin area) > > where a good scenario would mean using 2 plugins. What do we do for that > ? > > > > -Original Message- > > From: Jesse [mailto:purplecabb...@gmail.com] > > Sent: Monday, March 28, 2016 4:51 PM > > To: dev@cordova.apache.org > > Subject: Re: Adding Examples for Plugins in the ReadMe > > > > Awesome. > > I typically include a demo folder with inside my plugin repos, but this > > does mean that this demo code gets copied all over the place if a user > > installs a plugin via git-repo or clone. > > I npm-ignore the demo folder so at least it does not go to npm ... > > > > Here's an example: > > https://github.com/purplecabbage/phonegap-plugin-sidebar/ > > > > > > We could also create a cordova-demos repo in apache which has a demo > > project for each core plugin. > > > > Cheers, > > Jesse > > > > > > > > @purplecabbage > > > > > https://na01.safelinks.protection.outlook.com/?url=risingj.com&data=01%7c01%7cpanarasi%40microsoft.com%7c11a99a9b7d574cb3752408d35763e384%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7NrDVGF57%2f02i6dLIGOb9tKyJbxoj8QgVa3cyTUAKLg%3d > > > > On Mon, Mar 28, 2016 at 4:26 PM, Robert Posener > > wrote: > > > > > +500 > > > > > > Regards > > > *Rob Posener* > > > 0419 012 627 > > > > > > On 29 March 2016 at 08:47, Parashuram N > wrote: > > > > > > > Hey folks, > > > > > > > > At the moment, the sample code in our plugins is limited to only > > > > show basic usage of the API. While this is great for someone who has > > > > already written Cordova projects, I believe that we may need more > > > > examples for folks who are just getting started with Cordova. > > > > To improve our documentation, Norm has sent out a pull request with > > > > additional examples that show the typical use cases for the plugins > > > > - https://github.com/apache/cordova-plugin-geolocation/pull/74/files > > > > > > > > This PR is the first in a set of work that we would like to do, to > > > improve > > > > documentation for plugins. A few questions to the community about > > > > this direction > > > > > > > > > > > > 1. Is it ok to include this as a part of the README ? That > would > > > > increase the visibility of the examples much more. We could have a > > > > "REFERENCE" section that is for quick reference, and then this set > > > > of detailed examples showing how the plugins work. Anyone have > > > > objections to that ? Note that the README would be longer, but I > > > > think that should be > > > ok. > > > > Also note that the README is imported into the Cordova docs, so > > > > these examples will also show up there > > > > > > > > 2. Some of the example have links to full projects that use the > > > > plugin. We did not find a place on the Apache github organization to > > > > put > > > it > > > > all up, so they currently reside in a Microsoft-github organization. > > > > Is that ok ? Is there a place to put full fledged Cordova samples on > > > > the Apache repos ? > > > > > > > > > >
Re: [DISCUSS] Curating Apps
Julio "rejecting" sounds so harsh Since we removed the "add app" and "add tool" from the webpage, there is no process to submit something to be accepted or rejected I think right now my opinion is that a PMC member would need to do the leg work to review, propose something to be added, and do the work of adding it. PMC members always look out for the best interest of the project, but as always we have lazy consensus it should bring up to other PMC members to see if any would vote -1 for any good reason to no accept the content to be added. Like I said this is only my opinion of one way of getting something added to tools or apps on the website. On Tue, Mar 29, 2016 at 9:38 AM julio cesar sanchez wrote: > I bring the topic back again because recently a tool was rejected and the > author mailed us asking (and we have not answered him yet) > > So, are we rejecting tools too? > > The original topic was "[DISCUSS] Curating Apps" and all the messages were > about apps, except this one from Steve that mentions removing "add a tool" > and "add a plugin" > > "YES! Removing the "add a tool" and "add a plugin" is the best way to go. > Those PRs require way to much management. Leave it up to PMC to nominate > apps." > > > > > > 2015-10-24 3:24 GMT+02:00 Dmitry Blotsky : > > > Sure, Iām also down for removing the āadd your appā option. Switching to > > putting apps up only at our own discretion makes sense. My only concern > is > > that I personally havenāt tried out many Cordova apps, so I would expect > us > > to have a shortage of apps this way. But if other PMC members have apps > to > > suggest, then we should be good. > > > > To move forward with Carlosā proposal, we ought to: > > - curate the existing list > > - have someone explain the change of policy to the PRs still open > > > > Any takers for those two tasks? > > > > Kindly, > > Dmitry > > > > > On Oct 23, 2015, at 6:01 PM, Steven Gill > wrote: > > > > > > YES! Removing the "add a tool" and "add a plugin" is the best way to > go. > > > Those PRs require way to much management. Leave it up to PMC to > nominate > > > apps. > > > > > > On Fri, Oct 23, 2015 at 5:41 PM, Nikhil Khandelwal < > > nikhi...@microsoft.com> > > > wrote: > > > > > >> I like Carlos' proposal. Reviewing PRs for these apps and judging by > > >> whatever criteria we finally decide (however objective/subjective) > will > > not > > >> be worth our time. The volume of PRs over the last couple of weeks has > > been > > >> quite significant in this area. > > >> > > >> At the end of the day, we just need 5-10 showcase apps. > > >> > > >> -Nikhil > > >> > > >> -Original Message- > > >> From: Carlos Santana [mailto:csantan...@gmail.com] > > >> Sent: Friday, October 23, 2015 5:37 PM > > >> To: dev@cordova.apache.org > > >> Subject: Re: [DISCUSS] Curating Apps > > >> > > >> I think we make it more simpler, a PMC member to propose to add an app > > >> that he/she tried out and feels that it deserves to be show case as a > > good > > >> example of a great Cordova App. > > >> - remove the "add your app" > > >> - PMC members mails the list, that he evaluated the app and a short > > >> description on why to added and he is planning to added, and ask if > > someone > > >> opposed with a -1 > > >> - Like Joe said, we don't need a tons of Apps, just a few will satisfy > > the > > >> goal > > >> - The Apache way, if there are no -1 app get's added. > > >> > > >> > > >> > > >> > > >> On Wed, Oct 21, 2015 at 7:27 PM Dmitry Blotsky < > dblot...@microsoft.com> > > >> wrote: > > >> > > >>> Sounds like weāve got some (potentially mutually exclusive) points: > > >>> - request detailed app descriptions from submitters > > >>> - curate based on detailed criteria > > >>> - curate based on loose criteria > > >>> - only accept blog posts, and get rid of the showcase > > >>> - just accept all requests > > >>> > > >>> Should this be a proposal on cordova-discuss? Or does someone feel > > >>> like we have a consensus? The ultimate goal is to have something that > >
Re: [DISCUSS] Tools Release CLI/LIB 6.1.1
I agree, we can discuss later the release for cordova-commons - Carlos @csantanapr > On Mar 29, 2016, at 7:27 AM, Vladimir Kotikov (Akvelon) > wrote: > > Carlos, I've reviewed and merged these PRs. However the only two PRs that > need to be included into this release are #415 [1] and #416 [2]. The other > two are for cordova-common and I guess we have nothing to do with them for > now. > > Summarizing, the release notes for 6.1.1 will look like this: > > ### 6.1.1 (Mar 29, 2016) > * CB-10961 Error no such file or directory adding ios platform when plugins > present or required > * CB-10908 Reload the config.xml before writing the saved plugin > > [1] https://github.com/apache/cordova-lib/pull/415 > [2] https://github.com/apache/cordova-lib/pull/416 > > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Monday, March 28, 2016 10:50 PM > To: dev@cordova.apache.org > Subject: [DISCUSS] Tools Release CLI/LIB 6.1.1 > > I would like to see a patch release for the tools > > Interested if someone can review and merge these PRs and get include it in > the release: > > https://github.com/apache/cordova-lib/pull/418 > https://github.com/apache/cordova-lib/pull/417 > https://github.com/apache/cordova-lib/pull/416 > https://github.com/apache/cordova-lib/pull/415 > > - > 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] Tools Release CLI/LIB 6.1.1
I would like to see a patch release for the tools Interested if someone can review and merge these PRs and get include it in the release: https://github.com/apache/cordova-lib/pull/418 https://github.com/apache/cordova-lib/pull/417 https://github.com/apache/cordova-lib/pull/416 https://github.com/apache/cordova-lib/pull/415
Re: [Vote] Tools Release
Can you review this PR [1], I would like to get a fix for this problem on the next patch release [1]: https://github.com/apache/cordova-lib/pull/416 On Fri, Mar 25, 2016 at 9:58 AM Carlos Santana wrote: > I vote -1 > I think this is a critical problem we should fix > https://issues.apache.org/jira/browse/CB-10961 > > > On Fri, Mar 25, 2016 at 8:51 AM Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.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-10902 >> Tools have been published to dist/dev: >> https://dist.apache.org/repos/dist/dev/cordova/CB-10902/ >> >> The packages were published from their corresponding git tags: >> cordova-cli: 6.1.1 (ed5c366130) >> cordova-lib: 6.1.1 (96f89aa216) >> cordova-plugman: 1.2.1 (482b670510) >> >> 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 >> * Ensured continuous build was green when repos were tagged >> >> - >> Best regards, Vladimir >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org >> >>
Re: 6.1.0 (cordova-lib@undefined) ?
The malformed package published didn't have any functional impact, just extra files, So I don't see the need to do a release just for that, But I found a critical issue as I kept testing 6.1.0 more in depth Any way we should follow process as normal, do a CLI bug/patch 6.1.1 and have a [DISCUSS] on what should be in it like any bugs already fix in master and anything else that is almost ready/fix On Fri, Mar 25, 2016 at 10:18 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Hmm.. I thought the idea of 6.1.1 was to fix malformed package contents on > NPM and upload a correct package. > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Friday, March 25, 2016 4:18 PM > To: dev@cordova.apache.org > Subject: Re: 6.1.0 (cordova-lib@undefined) ? > > Vladimir, every Vote needs a new email thread "[DISCUSS]" so we can > discuss what would be in the new release > > I found a bad regression in 6.1.0, I think we should fix it and release > the fix with 6.1.1 Can you take a look at the JIRA and help fix > > As for the removing the cordova-common, let's do that in next patch > release maybe a 6.1.2, right now at least is critical for my work to get a > working 6.1.1, people are already using 6.1.0 and broke > > [1]: https://issues.apache.org/jira/browse/CB-10961 > > > On Fri, Mar 25, 2016 at 8:58 AM Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > > > I've started a vote thread. Voters are welcome :) > > > > Also I've notices that we bundle `cordova-common` into cordova-lib > > package. This is probably just a legacy of the time when > > cordova-common hadn't been released yet. > > However this is not a problem anymore so we should remove this > > `bundleDependencies` section? > > > > - > > Best regards, Vladimir > > > > -Original Message- > > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > > Sent: Friday, March 25, 2016 9:40 AM > > To: dev@cordova.apache.org > > Subject: RE: 6.1.0 (cordova-lib@undefined) ? > > > > I'll take care of it > > > > - > > Best regards, Vladimir > > > > -Original Message- > > From: Steven Gill [mailto:stevengil...@gmail.com] > > Sent: Thursday, March 24, 2016 7:11 PM > > To: dev@cordova.apache.org > > Subject: Re: 6.1.0 (cordova-lib@undefined) ? > > > > Shoot! So I am checking this out at the airport. > > > > So usually cordova-lib version is not supposed to show. It is for > > development only and I find it very useful. > > > > Looks like I made a mistake when publishing cordova-lib :( I was > > doing some tests to see what modules were being picked up when running > npm pack. > > I ended up not deleting those test files from cordova-lib directory > > and they got included. I published the tag from the repo when I should > > have npm published the tgz. My bad guys. It needs to get repackaged > > and published, but with npm, only way to do that is to bump version. > > So 6.1.1. Sucks that we have to vote for a repackage with no changes. > > > > Sorry. Can someone do this? > > > > -Steve > > On Mar 24, 2016 8:49 AM, "Carlos Santana" wrote: > > > > > Why do we need to print the version of cordova-lib inside CLI ? > > > > > > $ cordova -v > > > 6.1.0 (cordova-lib@undefined) > > > > > > I opened a JIRA [1] > > > > > > Do we want to remove the extra info of cordova-lib and only print > > > the CLI version? > > > > > > cordova-lib is a npm dependency on cordova-cli like any of the other > > > dependencies [2] > > > > > > Does someone using this extra info? > > > Do we need to provide more info or less info or provide more info > > > behind -d flag (i.e cordova -v -d)? > > > > > > [1]: > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fiss > > > ue > > > s.apache.org%2fjira%2fbrowse%2fCB-10952&data=01%7c01%7cv-vlkoti%40mi > > > cr > > > osoft.com%7c8eae6527f8614b78403808d353ff0b68%7c72f988bf86f141af91ab2 > > > d7 > > > cd011db47%7c1&sdata=Pvc1SOKl%2fgMyUhAwUP%2fRmlZzy%2buQV5OE7tzSJWbWhr > > > M% > > > 3d > > > [2]: > > > https://github.com/apache/cordova-cli/blob/master/package.json#L31 > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
Re: [Vote] Tools Release
I vote -1 I think this is a critical problem we should fix https://issues.apache.org/jira/browse/CB-10961 On Fri, Mar 25, 2016 at 8:51 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.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-10902 > Tools have been published to dist/dev: > https://dist.apache.org/repos/dist/dev/cordova/CB-10902/ > > The packages were published from their corresponding git tags: > cordova-cli: 6.1.1 (ed5c366130) > cordova-lib: 6.1.1 (96f89aa216) > cordova-plugman: 1.2.1 (482b670510) > > 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 > * Ensured continuous build was green when repos were tagged > > - > Best regards, Vladimir > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: 6.1.0 (cordova-lib@undefined) ?
Vladimir, every Vote needs a new email thread "[DISCUSS]" so we can discuss what would be in the new release I found a bad regression in 6.1.0, I think we should fix it and release the fix with 6.1.1 Can you take a look at the JIRA and help fix As for the removing the cordova-common, let's do that in next patch release maybe a 6.1.2, right now at least is critical for my work to get a working 6.1.1, people are already using 6.1.0 and broke [1]: https://issues.apache.org/jira/browse/CB-10961 On Fri, Mar 25, 2016 at 8:58 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > I've started a vote thread. Voters are welcome :) > > Also I've notices that we bundle `cordova-common` into cordova-lib > package. This is probably just a legacy of the time when cordova-common > hadn't been released yet. > However this is not a problem anymore so we should remove this > `bundleDependencies` section? > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Friday, March 25, 2016 9:40 AM > To: dev@cordova.apache.org > Subject: RE: 6.1.0 (cordova-lib@undefined) ? > > I'll take care of it > > - > Best regards, Vladimir > > -Original Message- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Thursday, March 24, 2016 7:11 PM > To: dev@cordova.apache.org > Subject: Re: 6.1.0 (cordova-lib@undefined) ? > > Shoot! So I am checking this out at the airport. > > So usually cordova-lib version is not supposed to show. It is for > development only and I find it very useful. > > Looks like I made a mistake when publishing cordova-lib :( I was doing > some tests to see what modules were being picked up when running npm pack. > I ended up not deleting those test files from cordova-lib directory and > they got included. I published the tag from the repo when I should have npm > published the tgz. My bad guys. It needs to get repackaged and published, > but with npm, only way to do that is to bump version. So 6.1.1. Sucks that > we have to vote for a repackage with no changes. > > Sorry. Can someone do this? > > -Steve > On Mar 24, 2016 8:49 AM, "Carlos Santana" wrote: > > > Why do we need to print the version of cordova-lib inside CLI ? > > > > $ cordova -v > > 6.1.0 (cordova-lib@undefined) > > > > I opened a JIRA [1] > > > > Do we want to remove the extra info of cordova-lib and only print the > > CLI version? > > > > cordova-lib is a npm dependency on cordova-cli like any of the other > > dependencies [2] > > > > Does someone using this extra info? > > Do we need to provide more info or less info or provide more info > > behind -d flag (i.e cordova -v -d)? > > > > [1]: > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue > > s.apache.org%2fjira%2fbrowse%2fCB-10952&data=01%7c01%7cv-vlkoti%40micr > > osoft.com%7c8eae6527f8614b78403808d353ff0b68%7c72f988bf86f141af91ab2d7 > > cd011db47%7c1&sdata=Pvc1SOKl%2fgMyUhAwUP%2fRmlZzy%2buQV5OE7tzSJWbWhrM% > > 3d > > [2]: > > https://github.com/apache/cordova-cli/blob/master/package.json#L31 > > >
6.1.0 (cordova-lib@undefined) ?
Why do we need to print the version of cordova-lib inside CLI ? $ cordova -v 6.1.0 (cordova-lib@undefined) I opened a JIRA [1] Do we want to remove the extra info of cordova-lib and only print the CLI version? cordova-lib is a npm dependency on cordova-cli like any of the other dependencies [2] Does someone using this extra info? Do we need to provide more info or less info or provide more info behind -d flag (i.e cordova -v -d)? [1]: https://issues.apache.org/jira/browse/CB-10952 [2]: https://github.com/apache/cordova-cli/blob/master/package.json#L31
Re: [ANNOUNCE] Tools Release!
Anyone having problems installing cordova cli 6.1.0 from npm? I tried this morning cordova help works it provided the update message āāāā ā Update available: 6.1.0 (current: 6.0.0) ā ā Run npm install -g cordova to update.ā āāāā But when I run npm install -g cordova cordova doesn't get installed, it looks like it installs cordova@1.0.0 but nothing get's installed I'm using npm@3.6.0 node@5.7.1 Then I run again with @latest npm install -g cordova@latest And this time it works Should we tell users to always use @latest when installing/upgrading as best practice? This will be places like the docs "Installing Cordova" [1] [2] [1]: http://cordova.apache.org [2]: http://cordova.apache.org/docs/en/latest/guide/cli/index.html On Wed, Mar 23, 2016 at 3:38 PM Steven Gill wrote: > Blog: http://cordova.apache.org/news/2016/03/23/tools-release.html > Tweet: https://twitter.com/apachecordova/status/712724158640054272 >
Re: GitHub pull request housekeeping
I have done cleaning by using coho instructions on other repos in the past You can close multiple PRs with one commit - Carlos @csantanapr > On Mar 23, 2016, at 4:10 PM, julio cesar sanchez > wrote: > > On cordova coho there is a section "Stale Pull Requests" > > To close a pull request that is no longer relevant / active: > > - Create an empty commit in the repo of the pull request via: > - `git commit --allow-empty -m "Closing stale pull request: close #99" > > So I think it can be done without editing the README.md (never tried) > > > I sometimes ask the PR owner to close it if it's not going to be merged, > but if he doesn't close it in a few days we can do this. > > > > > > 2016-03-23 21:05 GMT+01:00 Joe Bowser : > >> Hey >> >> So, I don't know about the other repositories, but cordova-android on >> GitHub has a lot of pull requests that are obviously never going to be >> accepted because they're out of date or are not on the master branch. >> Since we have no plans to merge things onto 3.7.x or the 4.1.x branches, it >> would be good if we could somehow close them. >> >> AFAIK, the only way we can close them is by editing README.md and putting >> in the git message. "This closes #", but it would be kind >> of annoying to have to do that. That said, may be we should do that for >> housekeeping. >> >> What do people think? >> >> Joe >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE] Cordova common 1.1.1 release
I vote +1 coho verify-archive coho verify-tags reproduce archives using coho create-archive On Tue, Mar 22, 2016 at 5:51 PM Shazron wrote: > I vote +1. > > * Ran coho verify-archive > * Verified tag > > > On Fri, Mar 18, 2016 at 6:00 PM, Steven Gill > wrote: > > Please review and vote on this cordova-common Release > > by replying to this email (and keep discussion on the DISCUSS thread) > > > > Release issue: https://issues.apache.org/jira/browse/CB-10911 > > > > Both tools have been published to > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-10911/ > > > > The packages were published from their corresponding git tags: > > cordova-lib: common-1.1.1 (80b70040bb) > > > > 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 > > * linked with cordova-lib and cordova-cli and ran npm test. > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [Vote] Tools Release March 18, 2016
I vote +1 coho verify-archive coho verify-tags reproduce archives using coho create-archive Only minor thing found cordova-lib.tgz/package/node_modules/ included more pacakges that it should, but not affect installation or functionality On Tue, Mar 22, 2016 at 5:53 PM Shazron wrote: > I vote +1. > > * Ran coho verify-archive > * Verified tags > > > On Fri, Mar 18, 2016 at 12:59 PM, Steven Gill > 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-10902 > > > > Both tools have been published to > > dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-10902/ > > > > The packages were published from their corresponding git tags: > > > > cordova-js: 4.1.4 (1482f4b4d1) > > cordova-lib: 6.1.0 (31b58d0c34) > > cordova-plugman: 1.2.0 (3426b27f17) > > cordova-cli: 6.1.0 (7b52ffccfb) > > > > 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 through testing section at > > > https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md#test > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests
I agree to enable config.xml to be able to set or override using config-file (i.e. any xml file including strings.xml) I also think that adding support in config.xml and plugin.xml to edit attributes is very helpful, this is exactly what we are doing for one of our plugin to add the attribute android:name for and it was a pain, and I think we still have problems doing it from before_plugin_install hook, it would be easier from plugin.xml On Tue, Mar 22, 2016 at 10:55 AM julio cesar sanchez wrote: > Yes, Simon, that's my opinion, and we should show the conficting values and > the id of the plugin with the conficting values so the user knows he has to > change the values on the config.xml or remove the plugin. > > But we still will have problems if the plugin uses a hook to write values > instead of using the config-file tag > > 2016-03-22 15:11 GMT+01:00 Alexis Kofman : > > > Maybe the configured values of the plugins are sometimes just default > > values that the user can override through the config.xml file. > > What about adding a flag indicating whether the value is overridable ? > My 2 > > cents ... > > > > On Tue, Mar 22, 2016 at 3:02 PM, Simon MacDonald < > > simon.macdon...@gmail.com> > > wrote: > > > > > So for Android's case you are thinking the order of precedence should > be: > > > > > > config.xml > > > plugin.xml > > > AndroidManifest.xml // created by the "cordova" cli > > > > > > Then if config.xml overrides something that one of the plugins depends > on > > > then the app won't build. I can actually get behind that proposal if > I'm > > > understanding you correctly. > > > > > > > > > Simon Mac Donald > > > http://hi.im/simonmacdonald > > > > > > On Tue, Mar 22, 2016 at 9:51 AM, julio cesar sanchez < > > > jcesarmob...@gmail.com > > > > wrote: > > > > > > > I think, if there is a conflict between config.xml and plugin.xml we > > > should > > > > not build. > > > > > > > > If we pick config.xml values, the plugins with conflicting values > might > > > not > > > > work, and if we pick the plugin.xml values, the app might not work > the > > > way > > > > the user wants. > > > > > > > > I think both options are bad, the user wants the plugin to work and > to > > > get > > > > the values he manually added and both aren't possible if there are > > > > conflicts. > > > > > > > > > > > > 2016-03-22 13:28 GMT+01:00 Simon MacDonald < > simon.macdon...@gmail.com > > >: > > > > > > > > > When it comes to the AndroidManifest if config.xml and plugin.xml > > > > (possibly > > > > > multiple plugin.xml's) disagree on the value of an attribute: > > > > > > > > > > - if the value is a boolean then it should default to 'false'. For > > > > instance > > > > > if it is an attribute like supports small screens if one plugin > sets > > it > > > > to > > > > > false it should be false for or else the app may not build. > > > > > - if the value is a integer then it should default to the highest > > > integer > > > > > provided. For instance minimum SDK version, again have to pick the > > > > highest > > > > > or the app won't build. > > > > > - if the value is a string, damned if I know if there are conflicts > > in > > > > > multiple plugin.xml files but plugin.xml should take precedence > over > > > > > config.xml. > > > > > > > > > > Sound reasonable? > > > > > > > > > > > > > > > Simon Mac Donald > > > > > http://hi.im/simonmacdonald > > > > > > > > > > On Tue, Mar 22, 2016 at 3:27 AM, Parashuram N < > > panar...@microsoft.com> > > > > > wrote: > > > > > > > > > > > The disagreement could also like in a āpreferenceā specifying a > > > value, > > > > > > that is overwritten by this fragment. > > > > > > > > > > > > On 3/21/16, 11:28 PM, "Jesse" wrote: > > > > > > > > > > > > >I like having the same xml fragments in config.xml as we use in > > > > > plugin.xml > > > > > > > > > > > > > > > > > > > > > > > > > > >parent="/manifest/application"> > > > > > > >https://na01.safelinks.protection.outlook.com/?url=com.foo.Foo&data=01%7c01%7cpanarasi%40microsoft.com%7c79eba6a8336a4e77391d08d3521b3bd2%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=MPgaRi3qGueHAnmnV6tXJyRlIzQIu6gHxeYTnpiKR9c%3d > > > > > > " > > > > > > >android:label="@string/app_name"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >We will need to address precedence, as a plugin.xml and > config.xml > > > can > > > > > > >disagree. > > > > > > > > > > > > > > > > > > > > > > > > > > > >> On Mar 21, 2016, at 12:46 PM, Shazron > > wrote: > > > > > > >> > > > > > > >> Continuing on Simon's point, we already have duplication of > > > entries > > > > > > >> for preference tags in > > > > > > > > > > > > > > > > > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9264&data=01%7c01%7cpanarasi%40microsoft.com%7c79eba6a8336a4e77391d08d3521b3bd2%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=Amj46nGpbpE
Re: [DISCUSS] cordova-ios release
I agree Steve - Carlos @csantanapr > On Mar 17, 2016, at 4:17 PM, Steven Gill wrote: > > Lets do a common release first and then follow that up with patch ios > release > >> On Thu, Mar 17, 2016 at 11:24 AM, Shazron wrote: >> >> I would say patch release. I had some items I wanted in the next >> release (labeled cordova-ios-4.1.1), but that shouldn't hold up >> releasing often, keep the train running... >> >> Ideally it should be accompanied with the patches I did yesterday for >> cordova-common (since cordova-common is bundled in to cordova-ios), >> but those bugs only really affect cordova-cli functionality >> >> On Thu, Mar 17, 2016 at 11:09 AM, Edna Y Morales >> wrote: >>> >>> Hi, >>> >>> We are interested in a cordova-ios release, specifically for this jira >>> item: https://issues.apache.org/jira/browse/CB-10773 >>> >>> Is there any opposition to this or any reason to wait? Steve would it >> make >>> sense to wait for a cordova-common release to happen first, before doing >>> the cordova-ios release? >>> >>> Would it be a patch release or a minor release? >>> >>> Thanks, >>> Edna Morales >> >> - >> 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: [ALL PLATFORMS][cordova-common] Platform specific preferences overridden by global preferences
changes are OK On Wed, Mar 16, 2016 at 5:05 PM Shazron wrote: > Pull requests sent, with tests: > > 1. https://github.com/apache/cordova-lib/pull/411 > > 2. https://github.com/apache/cordova-lib/pull/412 > > On Wed, Mar 16, 2016 at 11:13 AM, Nikhil Khandelwal > wrote: > > Thanks for the heads up. Good find! (1) sounds pretty bad - correct me > if I'm wrong, to fix this, we need to do the following: > > - fix it in cordova-common, release > > - bundle those changes to all platforms & release all of them. > > > > We need tests for this scenario also. > > > > Shaz: Are you planning to take all the tasks above? Some of us could > likely help. > > > > -Nikhil > > > > -Original Message- > > From: Shazron [mailto:shaz...@gmail.com] > > Sent: Wednesday, March 16, 2016 10:32 AM > > To: dev@cordova.apache.org > > Subject: [ALL PLATFORMS][cordova-common] Platform specific preferences > overridden by global preferences > > > > Some code changes I want to highlight that I want changing, in > cordova-common: > > > > 1. > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10694&data=01%7c01%7cnikhilkh%40microsoft.com%7c2393d3eed1794bcda84b08d34dc10912%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ynROJ1IjgLWqIcLk9AYH9%2fzlQTn%2fbVooUcyWk5iG12Q%3d > > > > Platform specific preferences are "overriden" by global preferences, > because when the merged config.xml file (root config.xml merge with > platform config.xml), the global preferences are written last always, so > they clobber any previous declaration. The change is to write platform > preferences last: > > > > > https://github.com/apache/cordova-lib/blob/a3285602b88f4e40f08c178b8b26c918c91d0dce/cordova-common/src/util/xml-helpers.js#L212-L217 > > > > 2. > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-9264&data=01%7c01%7cnikhilkh%40microsoft.com%7c2393d3eed1794bcda84b08d34dc10912%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=uKrVMPdcY2zBnYiGrTASEoKAlGoanmcdd6ME0BIlPd4%3d > > > > This is not as critical as #1 above, since it's just a build artifact > thing.This is just to remove duplicate entries in the merged config.xml. > > > > - > > 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: [DISCUSS] Cordova-common@1.1.1
Sounds good On Fri, Mar 18, 2016 at 7:21 PM Steven Gill wrote: > haha it would make my life easier. Too late now. I didn't include it in the > tools release but in hindsight I should have. > > Tools release will pick up this release since cordova-common dependency is > 1.1.x in cordova-lib. > > This cordova-common release has more to do with platforms anyways. The > changes in here need to be added to platforms for the fixes we want. Other > tools don't necessarily need this change to be released. They should come > out around the same time though. > > -Steve > > > > On Fri, Mar 18, 2016 at 4:03 PM, Carlos Santana > wrote: > > > Why cordova-common not included with the Tools release? > > Does the cordova-lib that you sent out to vote contains this fixes? I > > assuming it doesn't just want to be sure > > > > I think it can be release separately like any of the others, but > releasing > > it with the Tools would make it easier for person doing the Tools release > > in this case you Steve :-) > > > > > > On Fri, Mar 18, 2016 at 6:53 PM Steven Gill > > wrote: > > > > > I propose a patch release of cordova-common. Thoughts? > > > > > > Changes: > > > * CB-10694 - Update test to reflect merging of CB-9264 fix (removal of > > > duplicate entries) > > > * CB-10694 - Platform-specific configuration preferences don't override > > > global settings > > > * CB-9264 - Duplicate entries in config.xml > > > * CB-10791 Add adjustLoggerLevel to cordova-common.CordovaLogger > > > * CB-10662 Add tests for ConfigParser.getStaticResources > > > * CB-10622 fix target attribute being ignored for images in config.xml. > > > This closes #392 > > > * CB-10583 Protect plugin preferences from adding extra Array > properties. > > > This closes #400 > > > * CB-10626 Incremented cordova-common package version to -dev > > > > > > Issue: https://issues.apache.org/jira/browse/CB-10911 > > > > > >
Re: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios
Here is an example [1] of hooks created by ionic team member extending config.xml to allow user to configure their native sdk settings allowing have platforms as build artifacts. This could be a start at looking at some basic configuration settings via hooks cordova provides or just in cordova tooling (i.e. platformAPI parser) [1]: https://github.com/mhartington/cordova-config-utils On Tue, Mar 15, 2016 at 10:31 PM Carlos Santana wrote: > Scratch the "migrate cli command" idea. Now I think about it really messy > and it will be another hackHooks. > > I think we concentrate to provide more capabilities thru config.xml and > hooks for making migration more smooth. > > Like a running hooks on after_platform_update event and providing more > information in the hook context argument with from to platform info > > > > On Tue, Mar 15, 2016 at 9:52 PM Carlos Santana > wrote: > >> By "I like the proposal and deleting all previous versions I don't see as >> an issue." I meant that I don't have an issue if we don't have this feature >> to clean old. I prefer not to have it >> >> On Tue, Mar 15, 2016 at 9:51 PM Carlos Santana >> wrote: >> >>> I like the proposal and deleting all previous versions I don't see as an >>> issue. >>> >>> I didn't get the part of using symlinks, I don't symlinks they bring a >>> lot of problems to implement correctly I prefer we stick to real directory >>> and rename directories, user can choose to create symlinks on their needs, >>> we would just handle them. >>> >>> If end up doing a flag I prefer just deleting the one being replace, as >>> --no-backup >>> cordova platform update ios --no-backup (using nopt notation) >>> will do the rename ios -> ios@4.0.1 >>> will do the add ios >>> then only then if the add works and all plugins present get install and >>> cli exist with none zero go and don't save the backup and delete the folder >>> that was rename to ios@4.0.1 >>> >>> But I agree for now implement default to always do a backup, no flag >>> (maybe experimental) >>> >>> User needs to be explicit on harmful actions, they can do platform rm >>> ios@4.0.1 will simple delete /platforms/ios@4.0.1 >>> and he can do it for any platform current/active or old backups >>> >>> I'm OK about this proposal and we can start a new one that covers how to >>> help with migration. Since update becomes backup, >>> We need to think how much we invest in migration, value of cordova is on >>> the runtime (core platform, and plugins) >>> >>> We can do start iterating with implementing enablement but specific >>> migration tasks/actions are built on real experiences by the community. >>> Meaning plugins/extensions that are plugable to handle migration, today >>> peope do with hooks, I call those hackHooks :-), hooks that do hacks to >>> make platforms build artifacts and be able to restore everything that can't >>> be restore with platform+plugins+config.xml >>> >>> So the flow I see if as the following: >>> >>> cordova platform update ios >>> >>> mv platforms/ios platforms/ios@4.0.1 >>> add platforms/ios >>> >>> cordova migrate ios ios@4.0.1 >>> >>> This cli migrate command migrate helps user migrate things from 4.0.1 >>> (ios@4.0.1) to 4.1 (ios/current) >>> migrate will run the actions/tasks/extensions added by the user, this >>> actions/tasks/extensions (don't have a good name for migrations "things") >>> will be available on npm with keyword cordova:migrate >>> For example there can be a command "migrate add >>> cordova-migrate-entitlements" (this tasks migrate ios entitlements from an >>> old project to a new project) >>> this tasks/extension will be added to list of steps to do to automate >>> migration when cli command migrate runs >>> Cordova project can provide the tooling and maybe a handful (or zero) of >>> well known tasks for migration, but not more, the rest will come from the >>> community/3rd party to maintain and publish, this will be a way for people >>> like Darryl and Tommy that have knowledge on migration and hooks they can >>> convert those to migration npm packages to share. >>> >>> >>> >>> >>> >>> >>> On Mon, Mar 14, 2016 at 8:21 PM Jesse wrote: >>> >>>> Yeah, the simple a
Re: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios
yep I agree Julio about adding more power to config.xml, that's basically what Mike's hook those allow tag in config.xml On Wed, Mar 16, 2016 at 10:23 AM julio cesar sanchez wrote: > I like Jesse's proposal > > for #3 I think we should use a new command, I like cordova *downgrade* > platform > > As I usually read most cordova questions on stackoverflow, most people is > editing and tellign others to edit the .plist manually and doing some other > manual changes. I always point them to use hooks or plugins to do that, but > as it's harder they don't want to do it. > > BTW, I think we should add a way to write on the AndroidManifest.xml and > info.plist from the config.xml as phonegap build does, using the > config-file tag. Right now it's possible to use the config-file tag on > plugin.xml but not on config.xml > > > > > 2016-03-16 14:54 GMT+01:00 Carlos Santana : > > > Here is an example [1] of hooks created by ionic team member extending > > config.xml to allow user to configure their native sdk settings allowing > > have platforms as build artifacts. > > > > This could be a start at looking at some basic configuration settings via > > hooks cordova provides or just in cordova tooling (i.e. platformAPI > parser) > > > > [1]: https://github.com/mhartington/cordova-config-utils > > > > > > On Tue, Mar 15, 2016 at 10:31 PM Carlos Santana > > wrote: > > > > > Scratch the "migrate cli command" idea. Now I think about it really > messy > > > and it will be another hackHooks. > > > > > > I think we concentrate to provide more capabilities thru config.xml and > > > hooks for making migration more smooth. > > > > > > Like a running hooks on after_platform_update event and providing more > > > information in the hook context argument with from to platform info > > > > > > > > > > > > On Tue, Mar 15, 2016 at 9:52 PM Carlos Santana > > > wrote: > > > > > >> By "I like the proposal and deleting all previous versions I don't see > > as > > >> an issue." I meant that I don't have an issue if we don't have this > > feature > > >> to clean old. I prefer not to have it > > >> > > >> On Tue, Mar 15, 2016 at 9:51 PM Carlos Santana > > >> wrote: > > >> > > >>> I like the proposal and deleting all previous versions I don't see as > > an > > >>> issue. > > >>> > > >>> I didn't get the part of using symlinks, I don't symlinks they bring > a > > >>> lot of problems to implement correctly I prefer we stick to real > > directory > > >>> and rename directories, user can choose to create symlinks on their > > needs, > > >>> we would just handle them. > > >>> > > >>> If end up doing a flag I prefer just deleting the one being replace, > as > > >>> --no-backup > > >>> cordova platform update ios --no-backup (using nopt notation) > > >>> will do the rename ios -> ios@4.0.1 > > >>> will do the add ios > > >>> then only then if the add works and all plugins present get install > and > > >>> cli exist with none zero go and don't save the backup and delete the > > folder > > >>> that was rename to ios@4.0.1 > > >>> > > >>> But I agree for now implement default to always do a backup, no flag > > >>> (maybe experimental) > > >>> > > >>> User needs to be explicit on harmful actions, they can do platform rm > > >>> ios@4.0.1 will simple delete /platforms/ios@4.0.1 > > >>> and he can do it for any platform current/active or old backups > > >>> > > >>> I'm OK about this proposal and we can start a new one that covers how > > to > > >>> help with migration. Since update becomes backup, > > >>> We need to think how much we invest in migration, value of cordova is > > on > > >>> the runtime (core platform, and plugins) > > >>> > > >>> We can do start iterating with implementing enablement but specific > > >>> migration tasks/actions are built on real experiences by the > community. > > >>> Meaning plugins/extensions that are plugable to handle migration, > today > > >>> peope do with hooks, I call those hackHooks :-), hooks that do hacks > to >
Re: [DISCUSS] Cordova-common@1.1.1
Why cordova-common not included with the Tools release? Does the cordova-lib that you sent out to vote contains this fixes? I assuming it doesn't just want to be sure I think it can be release separately like any of the others, but releasing it with the Tools would make it easier for person doing the Tools release in this case you Steve :-) On Fri, Mar 18, 2016 at 6:53 PM Steven Gill wrote: > I propose a patch release of cordova-common. Thoughts? > > Changes: > * CB-10694 - Update test to reflect merging of CB-9264 fix (removal of > duplicate entries) > * CB-10694 - Platform-specific configuration preferences don't override > global settings > * CB-9264 - Duplicate entries in config.xml > * CB-10791 Add adjustLoggerLevel to cordova-common.CordovaLogger > * CB-10662 Add tests for ConfigParser.getStaticResources > * CB-10622 fix target attribute being ignored for images in config.xml. > This closes #392 > * CB-10583 Protect plugin preferences from adding extra Array properties. > This closes #400 > * CB-10626 Incremented cordova-common package version to -dev > > Issue: https://issues.apache.org/jira/browse/CB-10911 >
Re: Does Cordova have a problem making developers happy?
I agree Joe It's easy to create a stackoverflow subscription that emails you once a day. I have one that covers "cordova" "worklight" "mobilefirst" I tried to answer what I can, but reading it daily which is not every day that I get something probably most every other day with a few. At least reading all the new questions gives me a sense on what people are having problems on. On Thu, Mar 17, 2016 at 8:46 PM Joe Bowser wrote: > BTW: The last one was a joke. But in all honesty, we should all spend a > bit more time on Stack seeing what's going on there with our respective > products/distributions. > > On Thu, Mar 17, 2016 at 5:43 PM, Joe Bowser wrote: > > > > > > > On Thu, Mar 17, 2016 at 5:23 PM, Ryan J. Salva > > wrote: > > > >> Keep in mind that the answers are limited to the technologies that Stack > >> Overflow chooses to offer in their list of options. They have an "other" > >> option with a text box, but people's answers are largely driven by the > >> checkbox options. > >> > >> > > So, we somehow pissed off the Stack Overflow guys??? > > > > > > > >> > >> > >> Ryan J. Salva | Principal PM Manager > >> Visual Studio Tools for Apache Cordova > >> rsa...@microsoft.com > >> 425 706 5270 office > >> 206 612 5079 mobile > >> > >> -Original Message- > >> From: Joe Bowser [mailto:bows...@gmail.com] > >> Sent: Thursday, March 17, 2016 5:21 PM > >> To: dev > >> Subject: Re: Does Cordova have a problem making developers happy? > >> > >> On Thu, Mar 17, 2016 at 5:12 PM, Ryan J. Salva > >> wrote: > >> > >> > As I told some of my co-workers today: > >> > > >> > If you read the fine print, the actual statistic is ā% of developers > >> > who are developing with the language or tech but have not expressed > >> > interest in continuing to do so.ā Clearly, itās not a good list to be > >> > on, but developer behavior also doesnāt reflect their stated intent. > >> > NPM Stats show the number of Cordova downloads has actually doubled > >> > since the same time last year. > >> > > >> > Again, I donāt think this is a good list to appear onā¦ Iām just not > >> > sure what to make of it given developer behavior. > >> > > >> > >> I'd rather be on that list instead of not be on any list. I'd be more > >> concerned with the fact that we're on the "Losers" section of the > trending > >> tech with a 7% decrease in the number of questions, which indicate that > >> people either have no problems (not very likely) or are just giving > up. I > >> haven't been answering questions on Stack for a while, mostly because > >> they're using some third party framework like ionic or something else. > >> > >> I also find it interesting that people are hating on Cordova, and not > >> PhoneGap, Ionic, Taco or the other distributions. > >> > >> > >> > > >> > > >> > Ryan J. Salva | Principal PM Manager Visual Studio Tools for Apache > >> > Cordova rsa...@microsoft.com > >> > 425 706 5270 office > >> > 206 612 5079 mobile > >> > > >> > -Original Message- > >> > From: Joe Bowser [mailto:bows...@gmail.com] > >> > Sent: Thursday, March 17, 2016 5:08 PM > >> > To: dev > >> > Subject: Re: Does Cordova have a problem making developers happy? > >> > > >> > On Thu, Mar 17, 2016 at 5:03 PM, Jesse > wrote: > >> > > >> > > Never trust people's answers when you ask them what they like! They > >> > > are almost always wrong, and will tell you what they think they > >> > > like, or think they will seem cooler if they liked. > >> > > > >> > > > >> > +1 > >> > > >> > It's interesting that CoffeeScript is on this list and that it passed > >> > Cordova in most dreaded. I also wonder what would happen if we went > >> > on the WordPress mailing list and talked about how people were so > >> > unhappy with WordPress. > >> > > >> > > >> > > > >> > > > On Mar 17, 2016, at 5:04 AM, julio cesar sanchez > >> > > > > >> > > wrote: > >> > > > > >> > > > 2016 survey is out > >> > > > > >> > > > Most Dreaded technologies: > >> > > > > >> > > > Visual Basic79.5% > >> > > > WordPress 74.3% > >> > > > Matlab 72.8% > >> > > > Sharepoint 72.1% > >> > > > CoffeeScript71.0% > >> > > > LAMP 68.7% > >> > > > Cordova 66.9% > >> > > > Salesforce 65.4% > >> > > > Other 61.5% > >> > > > Perl 61.3% > >> > > > SQL Server & SQL 60.3% > >> > > > Objective-C 60.2% > >> > > > > >> > > > > >> > > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fsta > >> > > ck > >> > > overflow.com > %2fresearch%2fdeveloper-survey-2016%23technology-most-lo > >> > > ve > >> > > d-dreaded-and-wanted&data=01%7c01%7crsalva%40microsoft.com > %7c342aabb > >> > > 95 > >> > > ca84607ba2608d34ec16bfe%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata > >> > > =x SvTHrkLQ7Z4Z7CTctZ4rjFxaznfrPKVjqCkMzcUIpk%3d > >> > > > >> > > > >>
Re: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios
Scratch the "migrate cli command" idea. Now I think about it really messy and it will be another hackHooks. I think we concentrate to provide more capabilities thru config.xml and hooks for making migration more smooth. Like a running hooks on after_platform_update event and providing more information in the hook context argument with from to platform info On Tue, Mar 15, 2016 at 9:52 PM Carlos Santana wrote: > By "I like the proposal and deleting all previous versions I don't see as > an issue." I meant that I don't have an issue if we don't have this feature > to clean old. I prefer not to have it > > On Tue, Mar 15, 2016 at 9:51 PM Carlos Santana > wrote: > >> I like the proposal and deleting all previous versions I don't see as an >> issue. >> >> I didn't get the part of using symlinks, I don't symlinks they bring a >> lot of problems to implement correctly I prefer we stick to real directory >> and rename directories, user can choose to create symlinks on their needs, >> we would just handle them. >> >> If end up doing a flag I prefer just deleting the one being replace, as >> --no-backup >> cordova platform update ios --no-backup (using nopt notation) >> will do the rename ios -> ios@4.0.1 >> will do the add ios >> then only then if the add works and all plugins present get install and >> cli exist with none zero go and don't save the backup and delete the folder >> that was rename to ios@4.0.1 >> >> But I agree for now implement default to always do a backup, no flag >> (maybe experimental) >> >> User needs to be explicit on harmful actions, they can do platform rm >> ios@4.0.1 will simple delete /platforms/ios@4.0.1 >> and he can do it for any platform current/active or old backups >> >> I'm OK about this proposal and we can start a new one that covers how to >> help with migration. Since update becomes backup, >> We need to think how much we invest in migration, value of cordova is on >> the runtime (core platform, and plugins) >> >> We can do start iterating with implementing enablement but specific >> migration tasks/actions are built on real experiences by the community. >> Meaning plugins/extensions that are plugable to handle migration, today >> peope do with hooks, I call those hackHooks :-), hooks that do hacks to >> make platforms build artifacts and be able to restore everything that can't >> be restore with platform+plugins+config.xml >> >> So the flow I see if as the following: >> >> cordova platform update ios >> >> mv platforms/ios platforms/ios@4.0.1 >> add platforms/ios >> >> cordova migrate ios ios@4.0.1 >> >> This cli migrate command migrate helps user migrate things from 4.0.1 >> (ios@4.0.1) to 4.1 (ios/current) >> migrate will run the actions/tasks/extensions added by the user, this >> actions/tasks/extensions (don't have a good name for migrations "things") >> will be available on npm with keyword cordova:migrate >> For example there can be a command "migrate add >> cordova-migrate-entitlements" (this tasks migrate ios entitlements from an >> old project to a new project) >> this tasks/extension will be added to list of steps to do to automate >> migration when cli command migrate runs >> Cordova project can provide the tooling and maybe a handful (or zero) of >> well known tasks for migration, but not more, the rest will come from the >> community/3rd party to maintain and publish, this will be a way for people >> like Darryl and Tommy that have knowledge on migration and hooks they can >> convert those to migration npm packages to share. >> >> >> >> >> >> >> On Mon, Mar 14, 2016 at 8:21 PM Jesse wrote: >> >>> Yeah, the simple approach is probably the best! >>> >>> Move to strike --kill or any variation of it, and let developers delete >>> what they want to. If it proves to be an issue, then we will address it. >>> >>> >>> @purplecabbage >>> risingj.com >>> >>> On Mon, Mar 14, 2016 at 3:58 PM, Parashuram N >>> wrote: >>> >>> > Instead of adding an entire flag to remove previous versions, does it >>> make >>> > sense to have cordova platform android@oldVersion. Alternatively, >>> users >>> > could simple use the terminal to delete older versions from the command >>> > line inside the platform folders. >>> > If we have users asking for
Re: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios
By "I like the proposal and deleting all previous versions I don't see as an issue." I meant that I don't have an issue if we don't have this feature to clean old. I prefer not to have it On Tue, Mar 15, 2016 at 9:51 PM Carlos Santana wrote: > I like the proposal and deleting all previous versions I don't see as an > issue. > > I didn't get the part of using symlinks, I don't symlinks they bring a lot > of problems to implement correctly I prefer we stick to real directory and > rename directories, user can choose to create symlinks on their needs, we > would just handle them. > > If end up doing a flag I prefer just deleting the one being replace, as > --no-backup > cordova platform update ios --no-backup (using nopt notation) > will do the rename ios -> ios@4.0.1 > will do the add ios > then only then if the add works and all plugins present get install and > cli exist with none zero go and don't save the backup and delete the folder > that was rename to ios@4.0.1 > > But I agree for now implement default to always do a backup, no flag > (maybe experimental) > > User needs to be explicit on harmful actions, they can do platform rm > ios@4.0.1 will simple delete /platforms/ios@4.0.1 > and he can do it for any platform current/active or old backups > > I'm OK about this proposal and we can start a new one that covers how to > help with migration. Since update becomes backup, > We need to think how much we invest in migration, value of cordova is on > the runtime (core platform, and plugins) > > We can do start iterating with implementing enablement but specific > migration tasks/actions are built on real experiences by the community. > Meaning plugins/extensions that are plugable to handle migration, today > peope do with hooks, I call those hackHooks :-), hooks that do hacks to > make platforms build artifacts and be able to restore everything that can't > be restore with platform+plugins+config.xml > > So the flow I see if as the following: > > cordova platform update ios > > mv platforms/ios platforms/ios@4.0.1 > add platforms/ios > > cordova migrate ios ios@4.0.1 > > This cli migrate command migrate helps user migrate things from 4.0.1 > (ios@4.0.1) to 4.1 (ios/current) > migrate will run the actions/tasks/extensions added by the user, this > actions/tasks/extensions (don't have a good name for migrations "things") > will be available on npm with keyword cordova:migrate > For example there can be a command "migrate add > cordova-migrate-entitlements" (this tasks migrate ios entitlements from an > old project to a new project) > this tasks/extension will be added to list of steps to do to automate > migration when cli command migrate runs > Cordova project can provide the tooling and maybe a handful (or zero) of > well known tasks for migration, but not more, the rest will come from the > community/3rd party to maintain and publish, this will be a way for people > like Darryl and Tommy that have knowledge on migration and hooks they can > convert those to migration npm packages to share. > > > > > > > On Mon, Mar 14, 2016 at 8:21 PM Jesse wrote: > >> Yeah, the simple approach is probably the best! >> >> Move to strike --kill or any variation of it, and let developers delete >> what they want to. If it proves to be an issue, then we will address it. >> >> >> @purplecabbage >> risingj.com >> >> On Mon, Mar 14, 2016 at 3:58 PM, Parashuram N >> wrote: >> >> > Instead of adding an entire flag to remove previous versions, does it >> make >> > sense to have cordova platform android@oldVersion. Alternatively, users >> > could simple use the terminal to delete older versions from the command >> > line inside the platform folders. >> > If we have users asking for a way to āremove all older platformsā, we >> > could then introduce this flag. >> > >> > On 3/14/16, 2:07 PM, "Shazron" wrote: >> > >> > >Note: >> > >I prefer `--remove-previous-versions` to `--kill` so as to be >> > >unambiguous and explicit. >> > > >> > >On Mon, Mar 14, 2016 at 2:01 PM, Shazron wrote: >> > >> +1 I like it (esp reasons in #2) >> > >> >> > >> I agree that platform rm+add is not there yet, case in point all the >> > >> related issues in the "Issue Links" in this issue: >> > >> >> > >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10775&data=01%7c01%7
Re: [PROPOSAL] 'cordova platform update' alias for rm, add in cordova-ios
et confusing. If we have listing of the previous versions > > >> above in `cordova platform ls`, you would have to explicitly do a > > >> `cordova platform rm ios@4.0.1` for example. However, this does not > > >> solve for a way to remove *all* previous versions (we will have to > > >> figure out a new command?) > > >> > > >> > > >> On Mon, Mar 14, 2016 at 1:29 PM, Jesse > wrote: > > >>> Considering all of the points previously mentioned, I would like to > > make a > > >>> supplementary proposal. > > >>> > > >>> We seem to all agree that platform rm+add is ideal in a world where > we > > can > > >>> truly consider platforms as artifacts, but we are really not there > yet. > > >>> The zipped snapshot of the platform before the update that Carlos > > mentions > > >>> is a good non-destructive way of allowing a developer the chance to > > always > > >>> go back. > > >>> I would like to take this approach one step further and suggest: > > >>> (note: I am using 'ios' as the example platform, but this applies to > > >>> any/all platforms ) > > >>> > > >>> 1. when updating a project, we rename the previous platforms/ios/ to > > >>> include the version it was, and leave it in the platforms folder. > > >>> ex. platforms/ios/ -> platforms/ios@4.0.1/ > > >>> > > >>> 2. platforms/ios would always contain the latest ios version > installed > > for > > >>> this project. This would allow most tooling to work unchanged, and > > >>> sidesteps symlink issues on windows with things like ios-latest -> > > ios@4.02 > > >>> > > >>> 3. [optional or stretch goal] 'platform rm ios' could be used to go > > back to > > >>> the previous 'current' version ( according to semver ) or should this > > be a > > >>> new command? like 'cordova platform pop ios' ? > > >>> > > >>> 4. we can add a flag to platform update ios --kill to do a > destructive > > >>> update for users who know that that is what they want. > > >>> > > >>> 5. [optional | stretch ] allow build/run of platform artifacts as > > well, so > > >>> developers can run commands like : 'cordova run ios@4.0.1' > > >>> > > >>> 6. the platform listed in config.xml would always be the latest one, > > >>> regardless of how many artifacts were still around. > > >>> > > >>> Thoughts? Issues? Comments? > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> @purplecabbage > > >>> > > > https://na01.safelinks.protection.outlook.com/?url=risingj.com&data=01%7c01%7cpanarasi%40microsoft.com%7c224926aef1e64b5a937008d34c4cc8af%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=AYCfungKQfswLZClqFCBX2oacLlJixX8xOGAFiJjJcQ%3d > > >>> > > >>> On Wed, Mar 9, 2016 at 10:38 AM, Dan Polivy > > wrote: > > >>> > > >>>> As a user of cordova (and list lurker), I thought I'd chime in and > say > > >>>> Carlos hit on some very good points. In theory I like the idea of > > treating > > >>>> platforms like build artifacts, but in reality -- at least for my > > current > > >>>> usage -- things are far from that. Making this type of change will > > make my > > >>>> upgrades more challenging. I'm willing to live with that, but PLEASE > > make > > >>>> sure you do a backup (or tell the user to) "just in case" before > > nuking > > >>>> their directory. > > >>>> > > >>>> Right now, I find I do more native (non CLI) development on iOS > > compared > > >>>> to other platforms. I'd have to do a full inventory of all of my > > native > > >>>> customizations, but as Carlos mentions it is a combination of: > > >>>> > > >>>> - working around bugs/limitations in the tools > > >>>> - additional AppDelegate customizations for native analytics > > libraries and > > >>>> error handling as our app is remotely
Re: [DISCUSS] Tools Release
Sounds good. I'm working on this [1] it should be done by then to pick it up [1]: https://issues.apache.org/jira/browse/CB-10808 On Sun, Mar 13, 2016 at 6:09 PM Steven Gill wrote: > I'm planning on starting a tools release on Wed. Let me know if you need me > to look at anything. > > -Steve >
Re: [ANNOUNCE] Plugin Release
bump, can someone send out tweet? On Sat, Mar 12, 2016 at 8:28 PM Carlos Santana wrote: > Blog: http://cordova.apache.org/news/2016/03/12/plugin-release.html > > Can someone send the tweet out? > >
[ANNOUNCE] Plugin Release
Blog: http://cordova.apache.org/news/2016/03/12/plugin-release.html Can someone send the tweet out?
Re: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 splashscreen@3.2.1 statusbar@2.1.2
The vote has now closed. The results are: Positive Binding Votes: 3 Alexander Sorokin Edna Morales Carlos Santana Negative Binding Votes: 0 Other Votes: 0 The vote has passed. I will now publish to dist and npm On Thu, Mar 10, 2016 at 12:06 PM Edna Y Morales wrote: > +1 > > > * Ran mobilespec plugin tests (ios) > * Verified that hello world app be can built and run with plugins (ios) > * Verified tags with 'coho verify-tags' > > Thanks, > *Edna Morales* > > [image: Inactive hide details for "Alexander Sorokin (Akvelon)" > ---03/10/2016 05:20:32 AM---I vote +1. * Verified signatures and > hashes]"Alexander > Sorokin (Akvelon)" ---03/10/2016 05:20:32 AM---I vote +1. * Verified > signatures and hashes > > From: "Alexander Sorokin (Akvelon)" > To: "dev@cordova.apache.org" > Date: 03/10/2016 05:20 AM > Subject: RE: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 > splashscreen@3.2.1 statusbar@2.1.2 > -- > > > > > I vote +1. > > * Verified signatures and hashes > * Verified tags > * Verified that plugins can be added correctly to blank app > * Verified that blank app can be successfully built and ran (windows and > android) > * Verified that browserified app can be successfully built and ran > (windows and android) > * Ran smoke testing of mobilespec app (windows and android) > * Verified release notes > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com ] > Sent: Thursday, March 10, 2016 6:59 AM > To: dev@cordova.apache.org > Subject: [VOTE] Plugins Release camera@2.1.1 globalization@1.0.3 > splashscreen@3.2.1 statusbar@2.1.2 > > 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://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10820&data=01%7c01%7cv-alsoro%40microsoft.com%7c3bb1f1c33f834014cb0308d348985372%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=KzCVERC8MyeVLeVpWIcRSl7gTsv524%2fdYEr%2bi8t1450%3d > > The plugins have been published to dist/dev: > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdist.apache.org%2frepos%2fdist%2fdev%2fcordova%2fCB-10820%2f&data=01%7c01%7cv-alsoro%40microsoft.com%7c3bb1f1c33f834014cb0308d348985372%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=NA3rwF0RFbHpxo9nxYHPAwKggnKk3d5ORuKcL%2bAwkas%3d > > The packages were published from their corresponding git tags: >cordova-plugin-camera: 2.1.1 (37dd471d0e) >cordova-plugin-statusbar: 2.1.2 (f1aa062557) >cordova-plugin-globalization: 1.0.3 (37c3e61e12) >cordova-plugin-splashscreen: 3.2.1 (e877722bac) > > Upon a successful vote I will upload the archives to dist/, upload them to > the Plugins Registry, 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 mobilespec with new plugins > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > >
Re: [DISCUSS] Plugins release
My bad, I had the impression that that open source package don't need to pay, that an organization was able to be created and only when creating the first package to be private then that required payment. sorry for the confusion On Fri, Mar 11, 2016 at 3:14 PM Shazron wrote: > Ouch, at 80 cordova committers, it will cost us $560/month for an npm org > :^O > > On Fri, Mar 11, 2016 at 8:41 AM, Carlos Santana > wrote: > > Thanks Steve ! > > > > I will ask Laurie, maybe we get a golden ticket :-) > > > > > > On Fri, Mar 11, 2016 at 11:34 AM Steven Gill > wrote: > > > >> Gave you npm publish access to all of the plugins! > >> > >> I looked into npm orgs when they first released them. They don't offer a > >> free tier for open source yet. > >> > >> -Steve > >> > >> On Fri, Mar 11, 2016 at 7:49 AM, Carlos Santana > >> wrote: > >> > >> > If everything goes well with the VOTE I should be able to close it > this > >> > weekend. > >> > > >> > Can someone give me access to npm to publish? > >> > > >> > I was reading the slides of a talk by the CTO on the many uses of npm > >> [1], > >> > and I notice they talk about organizations and teams to manage access. > >> > > >> > Is creating a team/organization something useful that can help out > with > >> the > >> > Cordova packages on npm? > >> > > >> > [1]: > http://slides.com/seldo/fluent-many-uses-of-npm?token=6WiGQf4V#/33 > >> > > >> > > >> > > >> > On Wed, Mar 9, 2016 at 11:34 PM Carlos Santana > >> > wrote: > >> > > >> > > Blog post for review: > https://github.com/apache/cordova-docs/pull/550 > >> > > > >> > > > >> > > On Wed, Mar 9, 2016 at 10:17 PM Carlos Santana < > csantan...@gmail.com> > >> > > wrote: > >> > > > >> > >> Richard merge the fix for the camera plugin > >> > >> > >> > >> I'm in the process of adding this one: > >> > >> > >> > >>- CB-10825 <https://issues.apache.org/jira/browse/CB-10825> > >> android: > >> > >>Always request READ permission for gallery source > >> > >> > >> > >> > >> > >> On Wed, Mar 9, 2016 at 2:27 PM Carlos Santana < > csantan...@gmail.com> > >> > >> wrote: > >> > >> > >> > >>> OK Richard ping me on Slack when you have it ready. > >> > >>> > >> > >>> Here is the rest of the changes to be included in this release, > will > >> > >>> wait for CB-10825 for camera plugin > >> > >>> > >> > >>> > >> > >>> ## cordova-plugin-camera > >> > >>> > >> > >>> ### 2.1.1 (Mar 09, 2016) > >> > >>> * added apache license header to appium files > >> > >>> * CB-10720 Fixed spelling, capitalization, and other small issues. > >> > >>> * CB-10414: Adding focus handler to resume video when user comes > back > >> > on > >> > >>> leaving the app while preview was running > >> > >>> * Appium tests: adjust swipe distance on ** Android ** > >> > >>> * CB-10750 Appium tests: fail fast if session is irrecoverable > >> > >>> * Adding missing semi colon > >> > >>> * Adding focus handler to make sure filepicker gets launched when > app > >> > is > >> > >>> active on ** Windows ** > >> > >>> * CB-10128: **iOS** Fixed how checks access authorization to > camera & > >> > >>> library. This closes #146 > >> > >>> * CB-10636 Add JSHint for plugins > >> > >>> * CB-10639 Appium tests: Added some timeouts, Taking a screenshot > on > >> > >>> failure, Retry taking a picture up to 3 times, Try to restart the > >> > Appium > >> > >>> session if it's lost > >> > >>> * CB-10552 Replacing images in README.md. > >> > >>> * Added a lot of more cases to get the real path on ** Android ** > >> > >>> * CB-10625 ** Android ** getPicture fails when getting a photo > from > >> the > >> > >>> Photo Library
Re: [DISCUSS] Plugins release
Thanks Steve ! I will ask Laurie, maybe we get a golden ticket :-) On Fri, Mar 11, 2016 at 11:34 AM Steven Gill wrote: > Gave you npm publish access to all of the plugins! > > I looked into npm orgs when they first released them. They don't offer a > free tier for open source yet. > > -Steve > > On Fri, Mar 11, 2016 at 7:49 AM, Carlos Santana > wrote: > > > If everything goes well with the VOTE I should be able to close it this > > weekend. > > > > Can someone give me access to npm to publish? > > > > I was reading the slides of a talk by the CTO on the many uses of npm > [1], > > and I notice they talk about organizations and teams to manage access. > > > > Is creating a team/organization something useful that can help out with > the > > Cordova packages on npm? > > > > [1]: http://slides.com/seldo/fluent-many-uses-of-npm?token=6WiGQf4V#/33 > > > > > > > > On Wed, Mar 9, 2016 at 11:34 PM Carlos Santana > > wrote: > > > > > Blog post for review: https://github.com/apache/cordova-docs/pull/550 > > > > > > > > > On Wed, Mar 9, 2016 at 10:17 PM Carlos Santana > > > wrote: > > > > > >> Richard merge the fix for the camera plugin > > >> > > >> I'm in the process of adding this one: > > >> > > >>- CB-10825 <https://issues.apache.org/jira/browse/CB-10825> > android: > > >>Always request READ permission for gallery source > > >> > > >> > > >> On Wed, Mar 9, 2016 at 2:27 PM Carlos Santana > > >> wrote: > > >> > > >>> OK Richard ping me on Slack when you have it ready. > > >>> > > >>> Here is the rest of the changes to be included in this release, will > > >>> wait for CB-10825 for camera plugin > > >>> > > >>> > > >>> ## cordova-plugin-camera > > >>> > > >>> ### 2.1.1 (Mar 09, 2016) > > >>> * added apache license header to appium files > > >>> * CB-10720 Fixed spelling, capitalization, and other small issues. > > >>> * CB-10414: Adding focus handler to resume video when user comes back > > on > > >>> leaving the app while preview was running > > >>> * Appium tests: adjust swipe distance on ** Android ** > > >>> * CB-10750 Appium tests: fail fast if session is irrecoverable > > >>> * Adding missing semi colon > > >>> * Adding focus handler to make sure filepicker gets launched when app > > is > > >>> active on ** Windows ** > > >>> * CB-10128: **iOS** Fixed how checks access authorization to camera & > > >>> library. This closes #146 > > >>> * CB-10636 Add JSHint for plugins > > >>> * CB-10639 Appium tests: Added some timeouts, Taking a screenshot on > > >>> failure, Retry taking a picture up to 3 times, Try to restart the > > Appium > > >>> session if it's lost > > >>> * CB-10552 Replacing images in README.md. > > >>> * Added a lot of more cases to get the real path on ** Android ** > > >>> * CB-10625 ** Android ** getPicture fails when getting a photo from > the > > >>> Photo Library - Google Photos > > >>> * CB-10619 Appium tests: Properly switch to webview on ** Android ** > > >>> * CB-10397 Added Appium tests > > >>> * CB-10576: MobileSpec can't get results for **Windows**-Store 8.1 > > Builds > > >>> * chore: edit package.json license to match SPDX id > > >>> * CB-10539: Commenting out the verySmallQvga maxResolution option on > ** > > >>> Windows ** > > >>> * CB-10541: Changing default maxResoltion to be highestAvailable for > > >>> CameraCaptureUI on ** Windows ** > > >>> * CB-10113 ** Browser ** - Layer camera UI on top of all! > > >>> * CB-10502 ** Browser ** - Fix camera plugin exception in Chrome when > > >>> click capture. > > >>> * Adding comments > > >>> * Camera tapping fix on ** Windows ** > > >>> > > >>> ## cordova-plugin-statusbar > > >>> > > >>> ### 2.1.2 (Mar 09, 2016) > > >>> * Fix for CB-10752 status bar overlays the webview on ** iOS ** 6 in > > >>> some cases > > >>> * CB-10683 Fix wrong StatusBar.isVisible initial value on ** Windows > ** > > >>> * CB-10636 Add
Re: Android N
1. I don't have personal experience creating and managing a board, just talked about what I saw Steve and Shaz using it 2. 100% carefully evaluate and try to push new features to user land/ third party, I agree Joe with pushing to third-party, I was just pointing the obvious of plugin should not brake, similar what we did with permissions on Android M On Fri, Mar 11, 2016 at 11:27 AM Joe Bowser wrote: > 1. I don't want to use a Kanban board. > > 2. I did some initial investigation and the WebView on N isn't ready to be > used. There's crashes the moment you try and resize a cordova application, > and it's clear that we should probably wait until the next Developer > Preview before we do anything. > > As far as the other features of Android N, they are plugin related and > outside our immediate scope. If people want to add these features as > third-party features, that's cool, but we have enough existing bugs that I > don't want to start adding features like scoped access and Data Saver to > the plugins. > > On Fri, Mar 11, 2016 at 7:52 AM, Carlos Santana > wrote: > > > Can you create the board and add the initial tasks, then Joe can follow > up > > and keep adding as more things get discover. > > > > Karen from the IBM team will also give it a try and she can create > > tasks/issues and add to the board on what ever she founds > > > > > > On Fri, Mar 11, 2016 at 10:46 AM Simon MacDonald < > > simon.macdon...@gmail.com> > > wrote: > > > > > That is a great idea. The board worked quite well for Cordova iOS 4.0. > > > > > > Simon Mac Donald > > > http://hi.im/simonmacdonald > > > > > > On Fri, Mar 11, 2016 at 10:44 AM, Carlos Santana > > > > wrote: > > > > > > > I agree creating a JIRA Kaban board, don't know if that's the > > > terminology. > > > > I know Shaz used that for Cordova iOS 4.0 and it was useful to see > what > > > the > > > > tasks included in one place. > > > > > > > > > > > > On Fri, Mar 11, 2016 at 10:25 AM Simon MacDonald < > > > > simon.macdon...@gmail.com> > > > > wrote: > > > > > > > > > I flashed one of my phones with Android N and did some basic > testing > > > > > yesterday and Cordova-Android apps still work :) > > > > > > > > > > I believe Joe was going to look into multi-window support. We > should > > > > > probably create JIRA items for all the new Android N features so we > > can > > > > > track them. > > > > > > > > > > > > > > > Simon Mac Donald > > > > > http://hi.im/simonmacdonald > > > > > > > > > > On Fri, Mar 11, 2016 at 8:59 AM, Carlos Santana < > > csantan...@gmail.com> > > > > > wrote: > > > > > > > > > > > Have someone evaluated Cordova with API 24/Android N [1]? > > > > > > > > > > > > Multi-Windows sounds like good if we can support. > > > > > > Wondering if the Data Saver thing how will affect File Transfer > > > > > > Scoped directory access plugin accessing IO, camera, file, etc.. > > > > > > > > > > > > > > > > > > [1]: http://developer.android.com/preview/index.html > > > > > > > > > > > > > > > > > > > > >
Re: Android N
Can you create the board and add the initial tasks, then Joe can follow up and keep adding as more things get discover. Karen from the IBM team will also give it a try and she can create tasks/issues and add to the board on what ever she founds On Fri, Mar 11, 2016 at 10:46 AM Simon MacDonald wrote: > That is a great idea. The board worked quite well for Cordova iOS 4.0. > > Simon Mac Donald > http://hi.im/simonmacdonald > > On Fri, Mar 11, 2016 at 10:44 AM, Carlos Santana > wrote: > > > I agree creating a JIRA Kaban board, don't know if that's the > terminology. > > I know Shaz used that for Cordova iOS 4.0 and it was useful to see what > the > > tasks included in one place. > > > > > > On Fri, Mar 11, 2016 at 10:25 AM Simon MacDonald < > > simon.macdon...@gmail.com> > > wrote: > > > > > I flashed one of my phones with Android N and did some basic testing > > > yesterday and Cordova-Android apps still work :) > > > > > > I believe Joe was going to look into multi-window support. We should > > > probably create JIRA items for all the new Android N features so we can > > > track them. > > > > > > > > > Simon Mac Donald > > > http://hi.im/simonmacdonald > > > > > > On Fri, Mar 11, 2016 at 8:59 AM, Carlos Santana > > > wrote: > > > > > > > Have someone evaluated Cordova with API 24/Android N [1]? > > > > > > > > Multi-Windows sounds like good if we can support. > > > > Wondering if the Data Saver thing how will affect File Transfer > > > > Scoped directory access plugin accessing IO, camera, file, etc.. > > > > > > > > > > > > [1]: http://developer.android.com/preview/index.html > > > > > > > > > >
Re: [DISCUSS] Plugins release
If everything goes well with the VOTE I should be able to close it this weekend. Can someone give me access to npm to publish? I was reading the slides of a talk by the CTO on the many uses of npm [1], and I notice they talk about organizations and teams to manage access. Is creating a team/organization something useful that can help out with the Cordova packages on npm? [1]: http://slides.com/seldo/fluent-many-uses-of-npm?token=6WiGQf4V#/33 On Wed, Mar 9, 2016 at 11:34 PM Carlos Santana wrote: > Blog post for review: https://github.com/apache/cordova-docs/pull/550 > > > On Wed, Mar 9, 2016 at 10:17 PM Carlos Santana > wrote: > >> Richard merge the fix for the camera plugin >> >> I'm in the process of adding this one: >> >>- CB-10825 <https://issues.apache.org/jira/browse/CB-10825> android: >>Always request READ permission for gallery source >> >> >> On Wed, Mar 9, 2016 at 2:27 PM Carlos Santana >> wrote: >> >>> OK Richard ping me on Slack when you have it ready. >>> >>> Here is the rest of the changes to be included in this release, will >>> wait for CB-10825 for camera plugin >>> >>> >>> ## cordova-plugin-camera >>> >>> ### 2.1.1 (Mar 09, 2016) >>> * added apache license header to appium files >>> * CB-10720 Fixed spelling, capitalization, and other small issues. >>> * CB-10414: Adding focus handler to resume video when user comes back on >>> leaving the app while preview was running >>> * Appium tests: adjust swipe distance on ** Android ** >>> * CB-10750 Appium tests: fail fast if session is irrecoverable >>> * Adding missing semi colon >>> * Adding focus handler to make sure filepicker gets launched when app is >>> active on ** Windows ** >>> * CB-10128: **iOS** Fixed how checks access authorization to camera & >>> library. This closes #146 >>> * CB-10636 Add JSHint for plugins >>> * CB-10639 Appium tests: Added some timeouts, Taking a screenshot on >>> failure, Retry taking a picture up to 3 times, Try to restart the Appium >>> session if it's lost >>> * CB-10552 Replacing images in README.md. >>> * Added a lot of more cases to get the real path on ** Android ** >>> * CB-10625 ** Android ** getPicture fails when getting a photo from the >>> Photo Library - Google Photos >>> * CB-10619 Appium tests: Properly switch to webview on ** Android ** >>> * CB-10397 Added Appium tests >>> * CB-10576: MobileSpec can't get results for **Windows**-Store 8.1 Builds >>> * chore: edit package.json license to match SPDX id >>> * CB-10539: Commenting out the verySmallQvga maxResolution option on ** >>> Windows ** >>> * CB-10541: Changing default maxResoltion to be highestAvailable for >>> CameraCaptureUI on ** Windows ** >>> * CB-10113 ** Browser ** - Layer camera UI on top of all! >>> * CB-10502 ** Browser ** - Fix camera plugin exception in Chrome when >>> click capture. >>> * Adding comments >>> * Camera tapping fix on ** Windows ** >>> >>> ## cordova-plugin-statusbar >>> >>> ### 2.1.2 (Mar 09, 2016) >>> * Fix for CB-10752 status bar overlays the webview on ** iOS ** 6 in >>> some cases >>> * CB-10683 Fix wrong StatusBar.isVisible initial value on ** Windows ** >>> * CB-10636 Add JSHint for plugins >>> * CB-10047 fix ** iOS ** 8 deprecated warnings >>> >>> ## cordova-plugin-globalization >>> >>> ### 1.0.3 (Mar 09, 2016) >>> * CB-10792 -Cannot install cordova-plugin-globalization with >>> cordova-windows on Ubuntu >>> * CB-10636 Add JSHint for plugins >>> * Minor changes to readme >>> * CB-10605 fix deprecation warnings on ** iOS ** >>> * chore: edit package.json license to match SPDX id >>> >>> ## cordova-plugin-splashscreen >>> >>> ### 3.2.1 (Mar 09, 2016) >>> * CB-10764: Remove emoji in cordova-plugin-splashscreen >>> * CB-10650 Non-index content.src causes Splashscreen to be not displayed >>> on ** Browser ** >>> * CB-10636 Add JSHint for plugins >>> * CB-10606 fix deprecation warning for interfaceOrientation on ** iOS ** >>> * chore: edit package.json license to match SPDX id >>> >>> On Wed, Mar 9, 2016 at 2:18 PM Richard Knoll >>> wrote: >>> >>>> I just found a critical camera bug[1], so we should hold off on that >>>> one. I think the fix is pretty simple, so I'll try and get a PR for it >>&
Re: Android N
I agree creating a JIRA Kaban board, don't know if that's the terminology. I know Shaz used that for Cordova iOS 4.0 and it was useful to see what the tasks included in one place. On Fri, Mar 11, 2016 at 10:25 AM Simon MacDonald wrote: > I flashed one of my phones with Android N and did some basic testing > yesterday and Cordova-Android apps still work :) > > I believe Joe was going to look into multi-window support. We should > probably create JIRA items for all the new Android N features so we can > track them. > > > Simon Mac Donald > http://hi.im/simonmacdonald > > On Fri, Mar 11, 2016 at 8:59 AM, Carlos Santana > wrote: > > > Have someone evaluated Cordova with API 24/Android N [1]? > > > > Multi-Windows sounds like good if we can support. > > Wondering if the Data Saver thing how will affect File Transfer > > Scoped directory access plugin accessing IO, camera, file, etc.. > > > > > > [1]: http://developer.android.com/preview/index.html > > >
Re: [Android] New Bridge: evaluateJavascript
Maybe we can do a Cordova Android 6.0 and sync it with Android N support when it comes out and this new bridge. On Thu, Mar 10, 2016 at 7:29 PM Joe Bowser wrote: > On Thu, Mar 10, 2016 at 3:54 PM, Darryl Pogue wrote: > > > If it's an addition to one of the public interfaces, doesn't that > require a > > major bump because every existing implementation of the interface would > now > > cause errors due to missing methods? > > > > > Yeah, I hate semver. Right now we only have one existing implementation > (Crosswalk), and that's the only thing that's affected by it. If people > didn't think "Oh, it's a major version, everything is going to be > broken!!!" just because we added literally one call, I'd probably not have > an issue with the practice, but because of semver, this change is going to > probably be delayed because people don't want to jump another major version > so soon. > > As far as avoiding it, well, you kind of can't without using reflection to > determine whether your view has that method it begin with. Having to come > up with a technical solution to people's fear of bigger version numbers is > how we get more bugs in our code. > > Semver aside, this change sounds good to me. I've definitely encountered > > some bizarre issues with the online/offline events being used for bridge > > communication (like navigator.online getting permanently toggled to > false). > > > > Can you reproduce this reliably? I've asked for repro code from the person > who mentioned this, but I can't get it for unknown reasons. > > > > > > > On 10 March 2016 at 15:48, Carlos Santana wrote: > > > > > I didn't say it was a private API what I meant is that based on what > you > > > shared that this Will be a new public API another bridge people can use > > > with the current API not broken. > > > > > > So a minor bump on the version is OK > > > > > > - Carlos > > > @csantanapr > > > > > > > On Mar 10, 2016, at 4:03 PM, Joe Bowser wrote: > > > > > > > > Well, If they add the method, the latest version of their plugin > should > > > > still work with older versions of Cordova. So, is this really the > same > > > > thing? > > > > > > > > On Thu, Mar 10, 2016 at 12:18 PM, Simon MacDonald < > > > simon.macdon...@gmail.com > > > >> wrote: > > > > > > > >> I think we are okay bumping the minor for this change not the major. > > > >> > > > >> I'm in favour of this bridge as long as we don't need to guard all > the > > > code > > > >> with reflection. Using reflection to call evaluateJavascript would > > > negate > > > >> any performance bonus. So if we can use evaluateJavascript on > Android > > > 4.4 > > > >> and above and then revert to LoadUrl on Android 4.3 and earlier for > > this > > > >> bridge I say we go for it. > > > >> > > > >> I think we can give CrossWalk enough time so this doesn't completely > > > screw > > > >> them over. Also, if we give them a heads up they can make it so the > > > plugin > > > >> only installs on Cordova Android 5.1.1 and earlier. > > > >> > > > >> > > > >> Simon Mac Donald > > > >> http://hi.im/simonmacdonald > > > >> > > > >>> On Thu, Mar 10, 2016 at 2:51 PM, Joe Bowser > > wrote: > > > >>> > > > >>> On Thu, Mar 10, 2016 at 11:48 AM, Carlos Santana < > > csantan...@gmail.com > > > > > > > >>> wrote: > > > >>> > > > >>>> I don't think we need to bump major number, there is no public API > > > >> brake > > > >>> This isn't a private API. This API is how third parties like Intel > > can > > > >>> make things like Crosswalk. > > > >>> > > > >>> > > > >>>> we are just added a feature, old stuff will still work. > > > >>> > > > >>> Except that Crosswalk now has to implement evaluateJavascript on > > their > > > >>> XWalkEngine class. At least this won't need a crap ton of > reflection > > > >> code > > > >>> like the last API change. > > > >>> > > > >>>
Android N
Have someone evaluated Cordova with API 24/Android N [1]? Multi-Windows sounds like good if we can support. Wondering if the Data Saver thing how will affect File Transfer Scoped directory access plugin accessing IO, camera, file, etc.. [1]: http://developer.android.com/preview/index.html
Re: Simplifying cordova-cli README
Thanks Nikhil this looks very clean now +1 - Carlos @csantanapr > On Mar 10, 2016, at 8:22 PM, Nikhil Khandelwal wrote: > > Our cordova-cli readme has become super long & not been maintained over the > years. It repeats a lot of content from the docs. I have simplified it > significantly by linking to relevant getting started, filing issues, > contribution etc. sections that are part of our website. This should help > maintenance as we do not repeat ourselves. However, there is a loss of some > inline content. > > Please review and comment on this PR: > https://github.com/apache/cordova-cli/pull/240/files > > -Nikhil - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Removing plugin pinning
+1 - Carlos @csantanapr > On Mar 10, 2016, at 8:36 PM, Shazron wrote: > > +1 > >> On Thu, Mar 10, 2016 at 1:16 PM, Richard Knoll wrote: >> Hey everyone, >> >> With the new plugin version selection code merged into cordova-lib, are >> there any objections to removing plugin pinning? I plan to open PRs soon on >> the core plugins to move engine info into each plugin's package.json. >> >> Thanks, >> Richard > > - > 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: [DRAFT] [REPORT] Cordova - March 2016
LGTM - Carlos @csantanapr > On Mar 10, 2016, at 8:28 PM, Shazron wrote: > > Please read and review. I'm sending this out later tonight. > > https://github.com/cordova/apache-board-reports/blob/master/2016/2016-03.md > > - > 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: [Android] New Bridge: evaluateJavascript
I didn't say it was a private API what I meant is that based on what you shared that this Will be a new public API another bridge people can use with the current API not broken. So a minor bump on the version is OK - Carlos @csantanapr > On Mar 10, 2016, at 4:03 PM, Joe Bowser wrote: > > Well, If they add the method, the latest version of their plugin should > still work with older versions of Cordova. So, is this really the same > thing? > > On Thu, Mar 10, 2016 at 12:18 PM, Simon MacDonald > wrote: > >> I think we are okay bumping the minor for this change not the major. >> >> I'm in favour of this bridge as long as we don't need to guard all the code >> with reflection. Using reflection to call evaluateJavascript would negate >> any performance bonus. So if we can use evaluateJavascript on Android 4.4 >> and above and then revert to LoadUrl on Android 4.3 and earlier for this >> bridge I say we go for it. >> >> I think we can give CrossWalk enough time so this doesn't completely screw >> them over. Also, if we give them a heads up they can make it so the plugin >> only installs on Cordova Android 5.1.1 and earlier. >> >> >> Simon Mac Donald >> http://hi.im/simonmacdonald >> >>> On Thu, Mar 10, 2016 at 2:51 PM, Joe Bowser wrote: >>> >>> On Thu, Mar 10, 2016 at 11:48 AM, Carlos Santana >>> wrote: >>> >>>> I don't think we need to bump major number, there is no public API >> brake >>> This isn't a private API. This API is how third parties like Intel can >>> make things like Crosswalk. >>> >>> >>>> we are just added a feature, old stuff will still work. >>> >>> Except that Crosswalk now has to implement evaluateJavascript on their >>> XWalkEngine class. At least this won't need a crap ton of reflection >> code >>> like the last API change. >>> >>> >>>> >>>>> On Thu, Mar 10, 2016 at 2:41 PM Joe Bowser wrote: >>>>> >>>>> Well, since the problem is with ONLINE_EVENT having a race condition, >>>>> earlier versions of Android would have to use the slower LOAD_URL >> with >>>>> known issues related to the input fields. There's more testing that >>>> needs >>>>> to be done, obviously, but it's worth adding the third bridge in the >>> next >>>>> major release. >>>>> >>>>> I'm just wondering how people feel about bumping another version. I >>>> don't >>>>> think our users understand that we use semver at all, which makes >>> things >>>>> extremely frustrating. >>>>> >>>>> >>>>> >>>>> On Thu, Mar 10, 2016 at 11:30 AM, Carlos Santana < >> csantan...@gmail.com >>>> >>>>> wrote: >>>>> >>>>>> But what about 4.3 and lower versions of Android? How do we support >>>> them? >>>>>> Do we use ONLINE_EVENT if we detect were are running on those >>> versions >>>> of >>>>>> Android? >>>>>> >>>>>> >>>>>> On Thu, Mar 10, 2016 at 1:36 PM Joe Bowser >>> wrote: >>>>>> >>>>>>> So, apparently some people are reporting that the ONLINE_EVENT >>> bridge >>>>>> that >>>>>>> we currently use by default in Android has a race condition when >>> you >>>>>> start >>>>>>> using more than one WebView in an application. Even though we >>>> decided >>>>> to >>>>>>> not support the case of having multiple webviews in an >> Application, >>>>> it's >>>>>>> still being used this way. >>>>>>> >>>>>>> Ideally, I would like to see us figure out how we can change the >>>> bridge >>>>>>> modes so that we don't have so many static classes, or at least >>>> change >>>>>> them >>>>>>> such that we're not tracing mutable states in static classes. >>>> However, >>>>>>> someone asked about evaluateJavascript and using that for the >>> bridge. >>>>> I >>>>>>> implemented that really quick here: >> https://github.com/infil00p/cordova-android/tree/building_brid
Re: Edit to Edit on Github for Docs
I agree Robert This points out that [1] Contribute page is missing the Edit button :-). If it was there you could've submitted the change Add to the list another way to help the project by clicking that Edit link and help out Advertise the "Edit Source on Github" link with some info how easy and how the changes will eventually make it in [1] http://cordova.apache.org/contribute/ - Carlos @csantanapr > On Mar 10, 2016, at 5:50 PM, Robert Posener wrote: > > In my confused mode (as documented in my last e-mail) when I was wondering > what does this "Edit" button do? I went looking for an answer on different > Cordova documentation and contributor web pages. No answer was found. I > would have thought it should be explained under "Contributing" somewhere > and saying that you don't need to be a committer or have a login and that > you can't stuff anything up and whatever you contribute will be reviewed by > a knowledgeable person before it is committed. > > Rob > > Regards > *Rob Posener* > 0419 012 627 > >> On 10 March 2016 at 23:47, Dmitry Blotsky wrote: >> >> Hey Robert, >> >> What do you mean by the āEditā button being documented? >> >> Also folks: here is a PR with a change addressing this discussion and a >> bit more: https://github.com/apache/cordova-docs/pull/551/files. >> >> Kindly, >> Dmitry >> >> On Mar 9, 2016, at 2:19 PM, Robert Posener > rposen...@gmail.com>> wrote: >> >> Also, can we add "Edit on GitHub" to Blog and Plugin pages, please. >> >> Regards >> *Rob Posener* >> 0419 012 627 >> >> On 10 March 2016 at 09:14, Robert Posener > rposen...@gmail.com>> wrote: >> >> I like "Edit on GitHub". >> >> I was never sure how far into "editing" clicking on the "Edit" button >> would take me before I hit some roadblock (like needing to be a committer, >> like having a GitHub login, like being part of the cordova in-crowd, etc) >> that meant that I had wasted my time. It would be nice to clarify this >> (eg, a hover tip like "No login necessary - Will be queued for review by >> committers"). >> Also... where is the "Edit" button documented? >> >> Rob >> >> Regards >> *Rob Posener* >> 0419 012 627 >> >> On 9 March 2016 at 10:29, Dmitry Blotsky > dblot...@microsoft.com>> wrote: >> >> I don't know if we have A/B testing capabilities, but I'm cool with >> changing the text to "Edit on GitHub". Also, we have like 10 open PRs for >> docs from contributors, so the buttons definitely work. :) >> >> I'll make the change for "Edit on GitHub" unless someone objects. >> >> Kindly, >> Dmitry >> >> -Original Message- >> From: Jesse [mailto:purplecabb...@gmail.com] >> Sent: Tuesday, March 8, 2016 11:26 AM >> To: dev@cordova.apache.org<mailto:dev@cordova.apache.org> >> Subject: Re: Edit to Edit on Github for Docs >> >> +1 to AB testing! >> >> >> On Mar 8, 2016, at 11:02 AM, Steven Gill > stevengil...@gmail.com>> >> wrote: >> >> Look at us talking UX. Lets do some AB testing while we are at ;) >> >> On Tue, Mar 8, 2016 at 10:54 AM, Nikhil Khandelwal >> mailto:nikhi...@microsoft.com>> >> wrote: >> >> +1 for trying "Edit on Github" - anything that _may_ increase >> contributions to the docs is welcome. :) >> >> -Nikhil >> >> -Original Message- >> From: Shazron [mailto:shaz...@gmail.com] >> Sent: Tuesday, March 8, 2016 10:26 AM >> To: dev@cordova.apache.org<mailto:dev@cordova.apache.org> >> Subject: Re: Edit to Edit on Github for Docs >> >> I'm ambivalent. "Edit" is concise, and I would think most are curious >> enough to just click and see? >> >> On Tue, Mar 8, 2016 at 8:50 AM, Carlos Santana > <mailto:csantan...@gmail.com>> >> wrote: >> The other day I was looking like crazy the doc source code that >> corresponded to the page that a user was asking here in dev list >> where was the source code, so I assume he also didn't see the "Edit" >> >> Then someone pointed out there is an "Edit" link/button at the top >> right side of each page. >> >> Then I saw another website, can't remember now, but they had "Edit >> on Github" and having the "on Github" capture my attention. >> >> Wha
Re: [Android] New Bridge: evaluateJavascript
I don't think we need to bump major number, there is no public API brake we are just added a feature, old stuff will still work. On Thu, Mar 10, 2016 at 2:41 PM Joe Bowser wrote: > Well, since the problem is with ONLINE_EVENT having a race condition, > earlier versions of Android would have to use the slower LOAD_URL with > known issues related to the input fields. There's more testing that needs > to be done, obviously, but it's worth adding the third bridge in the next > major release. > > I'm just wondering how people feel about bumping another version. I don't > think our users understand that we use semver at all, which makes things > extremely frustrating. > > > > On Thu, Mar 10, 2016 at 11:30 AM, Carlos Santana > wrote: > > > But what about 4.3 and lower versions of Android? How do we support them? > > Do we use ONLINE_EVENT if we detect were are running on those versions of > > Android? > > > > > > On Thu, Mar 10, 2016 at 1:36 PM Joe Bowser wrote: > > > > > So, apparently some people are reporting that the ONLINE_EVENT bridge > > that > > > we currently use by default in Android has a race condition when you > > start > > > using more than one WebView in an application. Even though we decided > to > > > not support the case of having multiple webviews in an Application, > it's > > > still being used this way. > > > > > > Ideally, I would like to see us figure out how we can change the bridge > > > modes so that we don't have so many static classes, or at least change > > them > > > such that we're not tracing mutable states in static classes. However, > > > someone asked about evaluateJavascript and using that for the bridge. > I > > > implemented that really quick here: > > > > > > https://github.com/infil00p/cordova-android/tree/building_bridges > > > > > > Basically, this should get around the whole bridge state problem since > > > we're executing the JS on the right webview every time instead of > trying > > to > > > manipulate a static variable that may or may not correspond to the > > webview > > > that we're using. Also, the benchmarking on this initially seems > > > comparable to ONLINE_EVENT. > > > > > > There's also the fact that it's a lot less code than ONLINE_EVENT, due > to > > > the whole state thing. The main thing that ONLINE_EVENT has over > > > evaluateJavascript is that it works on Jellybean (4.3 and lower). > > > > > > This branch does add a method to the API, and Crosswalk would have to > add > > > the same two lines of code to their WebView to allow evaluateJavascript > > to > > > work there as well as it does here. I did check to make sure their API > > > does support it before I added it. > > > > > > So, is this useful? Should we merge it in? Do we increment a major > > version > > > number for this? > > > > > > Joe > > > > > >
Re: [Android] New Bridge: evaluateJavascript
But what about 4.3 and lower versions of Android? How do we support them? Do we use ONLINE_EVENT if we detect were are running on those versions of Android? On Thu, Mar 10, 2016 at 1:36 PM Joe Bowser wrote: > So, apparently some people are reporting that the ONLINE_EVENT bridge that > we currently use by default in Android has a race condition when you start > using more than one WebView in an application. Even though we decided to > not support the case of having multiple webviews in an Application, it's > still being used this way. > > Ideally, I would like to see us figure out how we can change the bridge > modes so that we don't have so many static classes, or at least change them > such that we're not tracing mutable states in static classes. However, > someone asked about evaluateJavascript and using that for the bridge. I > implemented that really quick here: > > https://github.com/infil00p/cordova-android/tree/building_bridges > > Basically, this should get around the whole bridge state problem since > we're executing the JS on the right webview every time instead of trying to > manipulate a static variable that may or may not correspond to the webview > that we're using. Also, the benchmarking on this initially seems > comparable to ONLINE_EVENT. > > There's also the fact that it's a lot less code than ONLINE_EVENT, due to > the whole state thing. The main thing that ONLINE_EVENT has over > evaluateJavascript is that it works on Jellybean (4.3 and lower). > > This branch does add a method to the API, and Crosswalk would have to add > the same two lines of code to their WebView to allow evaluateJavascript to > work there as well as it does here. I did check to make sure their API > does support it before I added it. > > So, is this useful? Should we merge it in? Do we increment a major version > number for this? > > Joe >
