Re: [Discuss] Cordova-common release

Separate modules are tempting, but I think they'll make the release process much harder. On Fri, Sep 25, 2015 at 11:40 AM, Sergey Grebnov (Akvelon) < v-seg...@microsoft.com> wrote: > I tend to agree w/ Carlos here, but from practical side it might be very > hard to maintain and release such a gra

Re: Experimenting with API for cordova tooling

, Parashuram N (MS OPEN TECH) < panar...@microsoft.com> wrote: > Should we move this docs to cordova-discuss instead > -https://github.com/cordova/cordova-discuss ? > > On 4/24/15, 4:02 PM, "Mark Koudritsky" wrote: > > >I'm back from ApacheCon and vacation. Very

Re: Experimenting with API for cordova tooling

ce -lib hands off the project to the platform code, > > it's just go time. > > > > What do you think the next steps are in terms of your API shape and > > plans? Where do you see needing help most, where can I pitch in to get > > your project going more? > >

Experimenting with API for cordova tooling

>From today's hangout discussion, here are the links to our experiments with using cordova tooling via API rather than CLI. It is loosely based on my older experiments here https://github.com/kamrik/CordovaGulpTemplate But his time there is a separate wrapper that exposes a more object oriented A

Re: [DISCUSS] Cordova TOOLS release - 4.3.1

+1 for a quick tools release. On Tue, Apr 7, 2015 at 12:34 PM, Steven Gill wrote: > Yeah, android 4.0 would be minor bump for cli according to our versioning > strategy. So it could be 5.1.0. It would be nice to include it in 5 though > so it can jump on the visibility 5 will create. Marketing!

Re: [VOTE] Cordova-Plugin-Whitelist and Cordova-Plugin-Legacy-Whitelist Plugins Release (attempt 2)

> > > > > Mark - I like that idea as well. > > > > > > On Mon, Mar 30, 2015 at 6:33 PM, Ian Clelland > > > wrote: > > > > > > > On 30 Mar 2015 4:52 pm, "Mark Koudritsky" wrote: > > > > > > > > > > An

Re: [VOTE] Cordova-Plugin-Whitelist and Cordova-Plugin-Legacy-Whitelist Plugins Release (attempt 2)

t; well. Nothing is actually broken by publishing either app-hello-world or > plugin-whitelist until we release a version of tools that is pinned to the > new hello-world. > > > On Mon, Mar 30, 2015 at 3:40 PM, Mark Koudritsky > wrote: > > > Looks like this breaks on cordova

Re: [VOTE] Cordova-Plugin-Whitelist and Cordova-Plugin-Legacy-Whitelist Plugins Release (attempt 2)

Looks like this breaks on cordova-android 3.7.1 (currently latest released) cordova-app-hello-world requires the whitelist plugin whitelist plugin depends on cordova-android 4.0 via the engine tag The resulting error message is Plugin doesn't support this project's cordova-android version. cordov

Re: [DISCUSS] Cordova App Hello World Release 3.9.0

+1 The code that uses NPM version of cordova-app-hello-world in cordova-lib is currently on a branch . Should we merge it now to start using the npm version of hello world? On Mon, Mar 23, 2015 at 3:20

Re: [Vote] 3.8.0 Cordova App Hello World Release (attempt 3)

+1 Built and ran on - Android 5.0.2 on Nexus 7 - iOS simulator On Fri, Mar 13, 2015 at 2:32 PM, Steven Gill wrote: > Please review and vote on this 3.8.0 Cordova App Hello World Release. > > Release issue: https://issues.apache.org/jira/browse/CB-8645 > > Repos ready to be released have been p

Re: [Vote] 3.8.0 Cordova App Hello World Release (attempt 2)

+1 Built and ran the app on iOS simulator and Android on Nexus 7. On Fri, Mar 13, 2015 at 10:41 AM, Sergey Grebnov (Akvelon) < v-seg...@microsoft.com> wrote: > I vote +1 > > * Verified that app can be built and ran (android, windows, wp8) > > Thx! > Sergey > -Original Message- > From: St

Re: Consolidating platform specific code from different places in cordova-lib

rally cannot > > require('cordova-lib'); without an exception thrown. Yet all the > > cordova-lib tests pass. What does it say about the quality of the tests > ;) > > > > On Tue, Mar 10, 2015 at 6:24 PM, Jesse wrote: > > > > > Had a quick look,

Consolidating platform specific code from different places in cordova-lib

I've created a pull request with changes across cordova-lib that should make it much easier to consolidate the platform specific code in cordova-lib to reduce duplication and maybe eventually move this code to the platforms repos. https://github.com/apache/cordova-lib/pull/183 Feedback is welcome.

Re: CLI installation from master

Yes, the instructions look correct. If you dan't need to use the `plugman` command, you don't need cordova-plugman. On Fri, Feb 27, 2015 at 12:21 AM, Toda, Shingo wrote: > Hi devs > > I read through this document to know how I can install CLI from cloned > cordova-cli. > https://github.com/apach

Re: Move platform parsers from CLI to platforms

There are 2 main places in the lib with platform specific logic src/cordova/metadata/_parser.js src/plugman/platforms/.js Probably all of this logic should be moved to platforms. On Sun, Feb 8, 2015 at 4:36 AM, Josh Soref wrote: > +1 > ‎ > Sent from my BlackBerry 10 smartphone. > >

Re: Usage of jscs & JSHint in Cordova

k all the way up to the > filesystem root until it finds a config file (unless you set configurations > differently). Given that it's incredibly hard to get consensus on different > IDE preferences, I would shy away from any IDE specific benefits/problems. +1 > -Orig

Re: Usage of jscs & JSHint in Cordova

I added he jscs file in cordova-lib some time ago but didn't enforce it in npm test because that required more work in the code to get rid of the remaining style errors. Would be glad if someone invests the effort to make the code comply with the current (or modified) rules. Similar story for the

Re: Cordova/PhoneGap Local Install

The best known example of how to use local installs of command line tools is probably Grunt, a globally installed binary will always look for and invoke a local installation. I'm also experimenting with a Gulp based workflow for Cordova which uses local installs of cordova-lib and cordova-android/i

Re: MobileSpec for testing cordova-lib@rc

gins.cordova.io would just search npm based on a cordova > > > plugins keyword (like http://gruntjs.com/plugins) > > > > > +1 > > > > > > > > With the JS API workflow, users can write code in es6 and use a > > transpiler > > > (like https://www

Re: MobileSpec for testing cordova-lib@rc

from npm instead of cordova plugins > registry. Thoughts? > > On Thu, Jan 8, 2015 at 1:09 PM, Mark Koudritsky wrote: > > > On Thu, Jan 8, 2015 at 3:47 PM, Michal Mocny > wrote: > > > > > If we add node_modules to search path, will we be able to adjust whic

Re: MobileSpec for testing cordova-lib@rc

On Thu, Jan 8, 2015 at 3:47 PM, Michal Mocny wrote: > If we add node_modules to search path, will we be able to adjust which > versions of platforms/plugins it uses just by modifying package.json? > > Since platforms can be added by path. You can replace platforms = ['android'] with platforms = [

Re: MobileSpec for testing cordova-lib@rc

Josh, thanks for the suggestion. Added it here <https://github.com/kamrik/cordova-test-rc/commit/d3a1abeda45357c4cf32b28e6e63cc269d7d3bda> as process.env.HOME = path.join(__dirname, 'home'); On Thu, Jan 8, 2015 at 2:19 PM, Josh Soref wrote: > Mark Koudritsky wrote: > >

MobileSpec for testing cordova-lib@rc

Trying to run MobileSpec with the tools release candidate yesterday inspired me to write a script that would do it all with a single command and a local installation of cordova-lib@rc without affecting the global install/link. This also turned out to be a good example of how to use cordova via JS

Re: [Vote] Tools Release Jan 6, 2015

+1 Tests: - npm install -g cordova@rc - Built and ran the default HelloWorld app on Android - ran "coho verify-tags" On Wed, Jan 7, 2015 at 4:27 PM, Andrew Grieve wrote: > +1 > > * Confirmed sigs & hashes with `coho verify-archive` > * Verified sha1s match tags with `coho verify-tags` > * R

Re: Cordova-lib failing on master (stopping release)

This commit https://github.com/apache/cordova-lib/commit/b2e33f55e98f23116066f47f9b6ea5b49474d95c passed on both AppVeyor and Travis

Re: minSdkVersion conflict

If you you add this line to cordova project config.xml It should set the same value in AndroidManifest.xml during prepare. The code that deals with it is in cordova-lib/src/cordova/metadata/android_parser.js starting at line 259 On Mon, Dec 8, 2014 at 1:59 AM, Fu, Junwei wrote: > Hi, > > The C

Re: plugins supported on cordova-browser platform?

If you browse all the plugins in the registry http://plugins.cordova.io/#/viewAll and then click on "Filter by Platform", you can se those that have a tag in their plugin.xml Also this Jira issue has all the plugins that need some work for browser platform as sub-tasks https://issues.apache.org/j

Re: [VOTE] Tools Release, take 3

Ok, just published it all. Thanks for help and support. Another question, for blog post the instructions look as follows: cd cordova-website rake build svn st svn add blah.blah.blah svn commit -m "$JIRA Published blog post for tools release." The `svn st` shows a bunch of stuff I had no intention

[ANNOUNCEMENT] Tools Release

New cordova tools released: cordova@4.1.2 (the Cordova CLI) plugman@0.22.16 cordova-lib@4.1.2 cordova-js@3.7.2 You can view the release blog post at http://cordova.apache.org/news/2014/11/13/tools-release.html

Re: [VOTE] Tools Release, take 3

The vote has now closed. The results are: Positive Binding Votes: 3 - Parashuram Narasimhan - Sergey Grebnov - Mark Koudritsky Negative Binding Votes: 0 The vote has passed. On Thu, Nov 13, 2014 at 3:06 PM, Mark Koudritsky wrote: > Thanks for testing everyone, sending out an offic

Re: [VOTE] Tools Release, take 3

Thanks for testing everyone, sending out an official results email soon. Josh thanks for the fixes in blog post. I've merged them in. The blog post pull request also contains a change to the win ce

Re: [VOTE] Tools Release, take 3

On Thu, Nov 13, 2014 at 10:06 AM, Ray Camden wrote: > Mark, question about this: > > To update your tools: > > npm install -g cordova > npm install -g plugman > > > To be clear, a Œregular¹ user doesn¹t need to update plugman, right? > > At present the plugman npm package contains only the CLI to

[VOTE] Tools Release, take 3

Please review and vote on this Tools Release. Release issue: https://issues.apache.org/jira/browse/CB-7988 Packages have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-7988/ And to npm under @rc tag To test them out you can use: npm -g uninstall cordova npm

Re: [VOTE] Tools Release, take 3

Please also review the updated blog post: https://github.com/cordova/apache-blog-posts/blob/master/2014-11-10-tools-release.md

Re: [VOTE] Tools Release, take 2

(x86, x64, arm, anycpu). > • Ran app with target keys and version flags. > • Checked the release notes. > > Thx! > Sergey > -Original Message- > From: Mark Koudritsky [mailto:kam...@google.com] > Sent: Monday, November 10, 2014 3:31 PM > To: dev@cor

Re: [Urgent] Windows platform build issue due to expired certificate

If this will be windows and wp 3.7.1, I'll update the tools release candidates tomorrow. On Tue, Nov 11, 2014 at 3:48 PM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: > As a result of this certificate expiry, Cordova-windows for all users is > currently broken. Cordova wi

Re: plugin.xml config-file for json files

I was just having similar thoughts about getting info from the plugin to *.gradle files. Another option for JSON would be to bundle a JSON file with the same structure as manifest.webapp and have the FirefoxOS build script merge this file into manifest.webapp as one of the first steps. This will r

Re: [VOTE] Tools Release

uldn't happen often. When it does, it should be fairly quick > as long as we are using release branches (which we are doing according to > release doc). > > On Mon, Nov 10, 2014 at 2:16 PM, Mark Koudritsky > wrote: > > > This vote is cancelled. > > > > Bl

[VOTE] Tools Release, take 2

Please review and vote on this Tools Release. Release issue: https://issues.apache.org/jira/browse/CB-7988 Packages have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-7988/ And to npm under @rc tag To test them out you can use: npm -g uninstall cordova npm

Re: [VOTE] Tools Release

ks like I answered > not to the latest email last time. > https://github.com/apache/cordova-lib/pull/118/ > > Thx! > Sergey > -Original Message----- > From: Mark Koudritsky [mailto:kam...@google.com] > Sent: Monday, November 10, 2014 9:14 AM > To: dev@cordova.apache.org

Re: Review: Tools Release blog post

>Mark, I added you as owner to that Org. > > > >-Steve > > > >On Mon, Nov 10, 2014 at 11:30 AM, Mark Koudritsky > >wrote: > > > >> I got a permission denied error when trying to push to origin. Didn't > >> invest the time to investig

Re: Review: Tools Release blog post

/14, 11:27 AM, "Marcel Kinard" wrote: > > > >> Ah, missed that. > >> > >> On Nov 10, 2014, at 11:20 AM, Mark Koudritsky > wrote: > >> > >>> The two items under "Platform updates" are already links to those two > >>> posts. > >

Re: [VOTE] Tools Release

> > > windows for now doesn't contain subfolder "windows": > > "windows": { > > "hostos": ["win32"], > > "parser": "./metadata/windows_parser", > > "url": " > > https:

Re: Review: Tools Release blog post

announcements/2014/11/06/cordova-wp-windows-3.7.0.html > > On Nov 7, 2014, at 5:22 PM, Mark Koudritsky wrote: > > > Please review and send PRs! > > > https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md > >

Re: Review: Tools Release blog post

sed so that there's a version that uses the new > cordova-lib? It seems odd that it's in the announcement, but missing from > the releasenotes. > > On Fri Nov 07 2014 at 5:22:51 PM Mark Koudritsky > wrote: > > > Please review and send PRs! > > https://github.com/k

Re: [DISCUSS] Tools Release

cuss the version in these threads early on. If CLI or Lib > have changes other than new pinned platforms, we should update the version > accordingly based on semver. > > On Fri, Nov 7, 2014 at 11:00 AM, Marcel Kinard wrote: > > > Makes total sense. > > > > On Nov 7,

Review: Tools Release blog post

Please review and send PRs! https://github.com/kamrik/apache-blog-posts/blob/master/2014-11-10-tools-release.md

[VOTE] Tools Release

Please review and vote on this Tools Release. Release issue: https://issues.apache.org/jira/browse/CB-7988 Packages have been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-7988/ And to npm under @rc tag To test them out you can use: npm -g uninstall cordova npm

Re: [DISCUSS] Tools Release

Yup, started the process thinking it will be 4.0.1, changing to 4.1.0 and restarting. For the release process in general, it looks like it would be useful to decide on the intended version names very early in the process and send out the intended version names as part of the DISCUSS email, so that

Re: [DISCUSS] Tools Release

The platforms are out, starting the tools release process.​

Re: [ANNOUNCE] Cordova-iOS, Cordova-Windows, & Cordova-wp8 3.7.0 released

Awesome! Starting a tools release. On Thu, Nov 6, 2014 at 7:46 PM, Steven Gill wrote: > > http://cordova.apache.org/announcements/2014/11/06/cordova-wp-windows-3.7.0.html > http://cordova.apache.org/announcements/2014/11/06/cordova-ios-3.7.0.html > > Lets get that tools release out! Mark? > > -S

Re: Questions re: plugin variables

Variables should to be provided when adding the plugin E.g: cordova plugin add org.some.plugin --variable API_KEY=some_value Example of a plugin that uses variables: http://plugins.cordova.io/#/package/com.phonegap.plugins.facebookconnect Relevant places in the code in cordova-lib: Where

Re: [DISCUSS] Tools Release

Thu, Oct 30, 2014 at 2:34 PM, Shazron wrote: > > > >> That patch I talked about was merged in. cordova-ios is out for vote. > >> > >> On Thu, Oct 30, 2014 at 8:06 AM, Mark Koudritsky > >> wrote: > >> > >>> On Wed, Oct 29, 2014 at

Re: [DISCUSS] Tools Release

On Wed, Oct 29, 2014 at 6:40 PM, Shazron wrote: > Mark, this patch is important for us to get pulled in: > https://github.com/apache/cordova-lib/pull/116 > > The patch looks good to me. I haven't branched yet, just merge it in if everything else is ok with it. > On Wed, Oct 29, 2014 at 3:27 PM

[DISCUSS] Tools Release

I would like to start a tools release. Any outstanding patches to land? Thoughts? - Mark

Re: Node Hook?

Looks like cordova couldn't find where node is on your system. On Windows cordova is doing some hackish magic to deal with shebang lines. The code for this magic is in extractSheBangInterpreter . Not sure, but

Re: [Vote] Tools Release 3.6.3-0.2.13

I vote +1​ - Verified signatures and hashes - installed rc via npm - created, built and ran an android project on OS X

Re: [DISCUSS] shrinkwrap

> > > Mark, > I want to understand better your statement "resulted in a great deal of > confusion for contributors". Can you give more details about that. One simple case I had myself was when debugging a suspected problem with one of dependencies and wasting several hours to only discover that

Re: [DISCUSS] continuous build and release process

+1 for release branches, reverting version bumps feels really awkward +1 for more continuous integration. And just to make sure more people are aware of it, there is this buildbot running some CI http://108.170.217.131:8010/waterfall A half baked idea for a more automated release process: Talking

Re: [DISCUSS] shrinkwrap

> > I suggest that: > - The shrinkwrap exist in git at all times, not just during the release > process. > -1 for that. Having shrinkwrap at all times will result in postponed discovery of incompatibilities with newer versions (which are usually trickier than shrinkwrap problems) until you nuke nod

Re: Time to Update the Who's Who!

Can't edit the wiki as well, could you please add me. The username is kamrik. Thanks. On Thu, Aug 28, 2014 at 9:59 AM, Carlos Santana wrote: > Piotr I added Mozilla and you two under it. > > Let me know your username on the Wiki and I can add you as contributor to > do edits. > > > On Tue, Aug

Re: continuous integration woze

gt; warnings are either treated like errors, or ignored entirely. I'm for > > > treating warnings like errors in the first place > > > > > > > > > On Thu, Aug 21, 2014 at 1:53 PM, Marcel Kinard > > wrote: > > > > > > > I agree. My personal p

Re: continuous integration woze

If some tests are too strict or too flaky, we can and should fix or remove them altogether. I don't believe there is any value in warnings, they will accumulate and then people will largely ignore them. There are also tests running or real devices here: http://ci.cordova.io/

Re: continuous integration woze

AFAIK Travis only supplies a binary pass/fail status, so there is no such thing as a warning. A Travis check for pull request doesn't mark the entire build on master as failed, only that pull request. So there is no need to panic and "drop everything and fix the build", instead just "fix the build"

Re: Hangout link?

I'll send out another reminder on the mailing list and irc some 10 min before the thing next time. But really, I don't think this morning is sufficiently "before the time" for an email to get lost, if it is, get a mail client with better inbox search (e.g. Gmail ;) ) On Tue, Aug 19, 2014 at 5:53

Re: Hangout link?

It was a rare case where we finished on time :) (at about 17:10 EDT) On Tue, Aug 19, 2014 at 5:50 PM, Archana Naik wrote: > Is hangout still going on? Can someone post the link? > > Thanks > Archana >

Re: [Discuss] 3.6.0 Release

npm info cordova-blackberry10--- 404 npm info cordova-blackberry--- OK cli is looking for blackberry10 as npm name but it's blckberry. I think the altplatform: 'blackberry' in platforms.js can solve this.

Reminder: Cordova Hangout Today @4pm EDT, 1pm PDT

Help take meeting notes (and add to the agenda): https://docs.google.com/a/google.com/document/d/1y6BEnHfCtU_EDVczYiqzixqyHtkh5Wxm8ifsCVoMfcY/edit Public viewing url: http://www.youtube.com/watch?v=ct5Bg0Ovs04 Event Page: https://plus.google.com/events/c55g46ep5njgug1gs3ecs49th54 Join the conver

Re: Cordova workflows based on build systems / task runners

ths, but I guess thats just your sample > > > > gulpfile. Probably we would either publish a gulp plugin that takes > in > > > > args, or just leave this repo as boilerplate and let users tweak > > > > accordingly? > > > > > > > > I&#x

Re: cordova plugin save

In order to keep the plugins as project deps in package.json we need to sort out some details of treating plugins as npm packages first: 1) Plugins don't currently have package.json files, and list their deps in plugin.xml. 2) Are we ok with loosing the possibility of specifying platform specific

Re: Cordova Plugin Registry iOS frameworks

Plugins are published using "npm publish". As far as I understood, npm does not include symlinks by design [1] when packing a package. So I'm not sure about how we could start including symlinks while still using npm packages as distribution method. [1] https://github.com/npm/npm/issues/3310 On

Re: platform switches for Windows Universal Apps

store > alternative make sense. > > --windows-store might, or maybe --modern-app or --winrt ? > > > > Sent from my iPhone > > > >> On Aug 8, 2014, at 6:20 AM, Mark Koudritsky wrote: > >> > >> My 2 cents: > >> > >> - I prefer

Cordova workflows based on build systems / task runners

Hi all, Inspired by several recent conversations on this mailing list I've been thinking about a Cordova workflow based on some build system. As an experiment I've put together this app using Gulp and cordova-lib: https://github.com/kamrik/CordovaGulpTemplate To try it out git clone https://git

Re: [Vote] Tools Release for Android 3.5.1

+1 - Installed from archives https://dist.apache.org/repos/dist/dev/cordova/CB-7267/ - Built a test app on OSX and ran it on Android (Nexus 7 with KitKat). On Tue, Aug 12, 2014 at 12:31 PM, Sergey Grebnov (Akvelon) < v-seg...@microsoft.com> wrote: > +1 > > * Verified archives > * Performed fun

Re: Directory Structure - CLI directory config proposal

I like the way it looks now, but I would argue that we need to take it another step further and make it a CordovaProject class that should only be instantiated once and contain all the info of ProjectMeta + most of the info passed around in the ad-hoc opts objects. I'm somewhat against passing JSO

Re: platform switches for Windows Universal Apps

My 2 cents: - I prefer "phone" over "handset" as I don't like those overly dry formal names that got heavily overloaded with years but still give a false sense of better specificity. - --store is a very counter intuitive name for desktop apps for someone not exposed to the new Windo

Re: Experimenting with JSCS + JSHint in cordova-lib

personally am a little hesitant to have to follow a certain coding style > + am worried about outside contributors struggling with it. On the other > hand, it would be nice for code readability to have uniform/consistent > style. > > As long as we discuss what styles we want to use befor

Experimenting with JSCS + JSHint in cordova-lib

Just opened a pull request with an experimental JSCS config. Would be glad to get some feedback about this. My goal is to eventually run JSCS together with JSHint as part of `npm test`. This is a relatively liberal config that doesn't generate too many warnings with the existing code. https://gith

Re: missing documentation and missing major version bump

Thanks for updating the help, Josh. On Thu, Jul 31, 2014 at 11:16 AM, Josh Soref wrote: > This is now done. > > I only documented run initially because I didn't really want to think > through the code (prepare is an interesting odd case) and I knew it > applied to run. > > On 7/30/14, 11:45 AM,

Re: missing documentation and missing major version bump

> > I think the concern was more of using current default name > HelloCordova.pbxproj this will always be the name of the project, unless > you really, really know what you are doing and want to change it you can > specify in cli, shell script, or in config.xml project="changetothis">appname > My

Re: missing documentation and missing major version bump

On Wed, Jul 30, 2014 at 12:50 PM, Carlos Santana wrote: > For the prepare I was thinking hooks. > > Does all hooks receive all the command line arguments including the extra > ones? > Yes, it receives the entire command line string, like this execOpts.env.CORDOVA_CMDLINE = process.argv.join(' ');

Re: missing documentation and missing major version bump

I'll add to the docs for other commands. prepare actually does receive those extra args but it doesn't call any platform scripts, so there is nobody to pass them along to. create doesn't call any platform scripts as well, the subsequent "platform add" does, but allowing extra args to "cordova pla

Re: missing documentation and missing major version bump

> So that's how it works today on the release version with a magic "-- > all the stuff to pass down" at the end of the cordova cli command? Yes, since this commit (included in the currently released version) e

Re: missing documentation and missing major version bump

ould > properly implement the parsing of arguments using "-" or "--" or for now if > extraplatformargs contain position args they will get what they expect. > > > > On Wed, Jul 30, 2014 at 10:24 AM, Mark Koudritsky > wrote: > > > On Wed, Jul 30, 2014

Re: missing documentation and missing major version bump

On Wed, Jul 30, 2014 at 1:46 AM, Carlos Santana wrote: > Yep Michal I agree to update cli to pass down extra parameters to platform > scripts like it used. this allow for greater flexibility in platform > scripts and no hardcoded platform concerns in cli. No need to remove nopt > if the this can

Re: --usegit / --usenpm

The last git message you copied (CB-7002) is the first commit after branching off the last tools release at that time platforms were donwloaded from git by default. The "usegit" commit came later. The corresponding commit in cordova-lib is 71c380a CB-7100: Use npm based lazy-load by default looks

Re: Proposal: remove platform versions from platfroms.js

Part of the discussion is release flexibility vs predictability. My main problem is that currently we have neither. By default CLI downloads pinned versions of platforms but latest versions of plugins. Changing the concept of corodva project to something managed by npm is an interesting idea but i

Re: Proposal: remove platform versions from platfroms.js

> > Currently WebWorks ships specific versions of things. > If we had shipped unpinned versions of stuff, then eventually we would > have created projects which our UI wouldn't have recognized as valid > (because, they e.g. Didn't have a ".cordova", or a "hooks", or a "merges" > or whichever things

Proposal: remove platform versions from platfroms.js

Currently a release of our cli tools always downloads the same version of platform files which is hard-coded incordova/platforms.js . This makes it impossible to release new versions of platforms that would be u

Re: Add build status to github

It works now! Added AppVeyor badge to README. Thanks to Daniel Gruno from the Apache INFRA team.

Re: Add build status to github

Travis builds are up and running here https://travis-ci.org/apache/cordova-lib/builds For AppVeyor there is some problem (might be permissions, details in INFRA-8066 ). Sergey, did you have to check some special check boxes on AppVeyor to make the

Re: Add build status to github

-Original Message- > From: Mark Koudritsky [mailto:kam...@google.com] > Sent: Friday, July 18, 2014 11:13 PM > To: dev@cordova.apache.org > Subject: Re: Add build status to github > > I didn't. > I guess we also need to provide the INFRA people with some short > instr

Re: Add build status to github

t; @purplecabbage > risingj.com > > > On Fri, Jul 18, 2014 at 11:36 AM, Mark Koudritsky > wrote: > > > The test failure on Travis is in plugman/install spec. It seems to only > > happen with a fresh checkout, once you run the test second time, it works > > ok. I was bitten b

Re: Add build status to github

The test failure on Travis is in plugman/install spec. It seems to only happen with a fresh checkout, once you run the test second time, it works ok. I was bitten by this before. Maybe something with bad management of temp dirs. I'll investigate. For now just removing that spec file "fixes" the bu

Re: Add build status to github

> To: dev@cordova.apache.org > > Subject: RE: Add build status to github > > > > https://docs.saucelabs.com/reference/status-images/ > > On Jul 15, 2014 9:17 AM, "Brian LeRoux" wrote: > > > > > Or we could use SauceLabs (for all) > >

Re: Add build status to github

Ok, let's ask here. Does anybody have any strong preferences for either AppVeyor or TravisCI or both for cordova-lib? note, this is only about running "npm test" in cordova-lib.

Re: Add build status to github

options due to windows support required. > > Both looks good to me, but I need to double check Wercker supports VS2013 > > (msbuild12) since it requires to build cordova-windows (will investigate > > and respond). I also think is that Travic-CI is the most safe option for > > ot

Re: Tools release blog post review

Published. The site diff was way larger than it should've been (mostly white space related diff). Any site building settings I missed? On Thu, Jul 10, 2014 at 5:24 PM, Mark Koudritsky wrote: > Ok, added Michal's wording with the one line instruction from Anis. > Publishing it.​ >

Re: Tools release blog post review

Ok, added Michal's wording with the one line instruction from Anis. Publishing it.​

Re: Tools release blog post review

get > > bundled > > > in. > > > > > > To try out this experimental feature you need to add the --browserify > > > option to plugman like so: > > > > > > plugman uninstall|install --browserify --project [PROJECT] --plugin > > > [P

  1   2   3   >