[GitHub] cordova-plugin-splashscreen pull request: Update index.md

[Sanafan]

Github user Sanafan closed the pull request at:

https://github.com/apache/cordova-plugin-splashscreen/pull/24


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Vote] Tools Release 3.6.3-0.2.12

[Carlos Santana]

If you are going to respin then I agree remove connect from cordova-js

On Tuesday, September 16, 2014, Marcel Kinard  wrote:

> This vote is cancelled, due to a technical issue in the packaging. I will
> fix the issue, generate a new release candidate with a new version, and
> start a new vote thread.
>
> On Sep 16, 2014, at 3:51 PM, Marcel Kinard  > wrote:
>
> > Please review and vote on this Tools Release.
>
>

-- 
Carlos Santana

Re: [Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

This vote is cancelled, due to a technical issue in the packaging. I will fix 
the issue, generate a new release candidate with a new version, and start a new 
vote thread.

On Sep 16, 2014, at 3:51 PM, Marcel Kinard  wrote:

> Please review and vote on this Tools Release.

Re: [Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

I've been doing some playing around to understand this better. Here are the 3 
scenarios I tried:

1) link:
cd cordova-lib
rm -r node_modules
rm npm-shrinkwrap.json
npm link cordova-js
npm install
npm shrinkwrap

Result is that ALL the devDependencies from cordova-js are present in the 
cordova-lib shrinkwrap.json file. Bad.

2) directory install:
cd cordova-lib
rm -r node_modules
rm npm-shrinkwrap.json
npm install ../cordova-js
npm install
npm shrinkwrap

Result is that none of the devDependencies from cordova-js are present in the 
cordova-lib shrinkwrap.json file. Good.

3) registry install:
cd cordova-lib
rm -r node_modules
rm npm-shrinkwrap.json
npm install cordova-js (fetches from registry)
npm install
npm shrinkwrap

Result is that none of the devDependencies from cordova-js are present in the 
cordova-lib shrinkwrap.json file. Good.

So what I get from this is that having a linked dependency matters: the 
shrinkwrap command will grab everything in the submodule's directory tree even 
if it isn't listed as a dependency in the submodule's package.json. That feels 
like a flaw in the shrinkwrap command, especially when the shrinkwrap command 
is careful to check that the main module's node_modules matches its 
package.json dependencies. It seems to be treating the main module and the 
submodules differently.

On Sep 16, 2014, at 9:56 PM, Andrew Grieve  wrote:

>> It shouldn't matter if I had done an "npm link cordova-js" inside of
>> cordova-lib, correct?
> 
> This is the key! It *does* matter. shrinkwrap just records what it finds in
> your node_modules directory, symlinks and all! You always want to do a
> fresh rm -r & npm install before shrinkwrap to ensure you don't have
> extraneous modules in there.
> 
> That said, if you did that and it's still showing up, I don't know why that
> is :S

I did NOT clean out the node_modules before doing the shrinkwrap. My "npm link" 
is present. I wasn't aware this was necessary, and there isn't anything in the 
instructions about it.

Now that I know what to do, I'll update the instructions and respin the lib, 
plugman, and cli RCs. I've done it this many times, what's once more? :-/

On Sep 16, 2014, at 9:25 PM, Carlos Santana  wrote:

> By default, npm install will install all modules listed as dependencies.
> With the --production flag, npm will not install modules listed in
> devDependencies.

I did try "npm -g install --production cordova@rc" and it is still pulling in 
the devDependencies from cordova-js.

> I will just ignore the Warning on connect and not respin.

I'm a perfectionist, and don't want to see user confusion about the warning.

On a broader note, we definitely need to change how we handle the shrinkwrap 
BEFORE the release process. I'll send out a note tomorrow with some ideas.

Re: [Vote] Tools Release 3.6.3-0.2.12

[Andrew Grieve]

On Tue, Sep 16, 2014 at 5:47 PM, Marcel Kinard  wrote:

> Sorry I'm not following exactly what you mean. Do you mean cordova-lib
> instead of cordova-cli?
>
Probably :P. Whichever has the shrinkwrap


>
> I also don't expect devDependencies to get installed when I do "npm -g
> install cordova@rc".
>
> cordova-js has the devDependency on connect, and does not have a
> shrinkwrap. cordova-lib has a dependency on cordova-js, but does have a
> shrinkwrap. When I generate the shrinkwrap in cordova-lib, all of the
> devDependencies in cordova-js are appearing in the cordova-lib shrinkwrap.
> That seems to be where it starts to go wrong.
>
> cd cordova-lib
> rm -r node_modules
> rm npm-shrinkwrap
> npm install
> npm shrinkwrap
>
> ...and I see the cordova-js devDependencies in the cordova-lib shrinkwrap.
> That's wrong, correct?
>
> It shouldn't matter if I had done an "npm link cordova-js" inside of
> cordova-lib, correct?
>

This is the key! It *does* matter. shrinkwrap just records what it finds in
your node_modules directory, symlinks and all! You always want to do a
fresh rm -r & npm install before shrinkwrap to ensure you don't have
extraneous modules in there.

That said, if you did that and it's still showing up, I don't know why that
is :S


>
> I'm trying to figure out if I'm doing something wrong, or if the
> shrinkwrap command is misbehaving.
>
> On Sep 16, 2014, at 4:07 PM, Andrew Grieve  wrote:
>
> > You shouldn't be seeing devDependencies show up in cordova. I'd double
> make
> > sure that if you:
> >
> > cd cordova-cli
> > rm -r node_modules
> > rm npm-shrinkwrap.json
> > npm install
> > npm shrinkwrap
> >
> >
> > that you end up with an npm-shrinkwrap.json that includes the
> devDependency.
> >
> >
> > On Tue, Sep 16, 2014 at 4:01 PM, Marcel Kinard 
> wrote:
> >
> >> FYI, I am getting the following warning when I do "npm install
> cordova@rc
> >> ":
> >>
> >> npm WARN engine connect@1.8.5: wanted: {"node":">= 0.4.1 < 0.7.0"}
> >> (current: {"node":"0.10.31","npm":"1.4.23"})
> >>
> >> This is a devDependency in cordova-js, which I didn't change. If folks
> >> want this dependency changed to get rid of the warning, then it will
> mean
> >> respinning this tools release.
>
>

Re: [Vote] Tools Release 3.6.3-0.2.12

[Carlos Santana]

By default, npm install will install all modules listed as dependencies.
With the --production flag, npm will not install modules listed in
devDependencies.

I will just ignore the Warning on connect and not respin.

The warning is that connect is old from 2011, and I think is no longer need
it for cordova-js that I'm aware. we can remove it for the next release and
probably do a clean across all repos and see what else is stale to bump the
version or remove.

Also for next release lets "npm install --production" that way is less
files to be downloaded by end users when installing form npm.


On Tue, Sep 16, 2014 at 5:47 PM, Marcel Kinard  wrote:

> Sorry I'm not following exactly what you mean. Do you mean cordova-lib
> instead of cordova-cli?
>
> I also don't expect devDependencies to get installed when I do "npm -g
> install cordova@rc".
>
> cordova-js has the devDependency on connect, and does not have a
> shrinkwrap. cordova-lib has a dependency on cordova-js, but does have a
> shrinkwrap. When I generate the shrinkwrap in cordova-lib, all of the
> devDependencies in cordova-js are appearing in the cordova-lib shrinkwrap.
> That seems to be where it starts to go wrong.
>
> cd cordova-lib
> rm -r node_modules
> rm npm-shrinkwrap
> npm install
> npm shrinkwrap
>
> ...and I see the cordova-js devDependencies in the cordova-lib shrinkwrap.
> That's wrong, correct?
>
> It shouldn't matter if I had done an "npm link cordova-js" inside of
> cordova-lib, correct?
>
> I'm trying to figure out if I'm doing something wrong, or if the
> shrinkwrap command is misbehaving.
>
> On Sep 16, 2014, at 4:07 PM, Andrew Grieve  wrote:
>
> > You shouldn't be seeing devDependencies show up in cordova. I'd double
> make
> > sure that if you:
> >
> > cd cordova-cli
> > rm -r node_modules
> > rm npm-shrinkwrap.json
> > npm install
> > npm shrinkwrap
> >
> >
> > that you end up with an npm-shrinkwrap.json that includes the
> devDependency.
> >
> >
> > On Tue, Sep 16, 2014 at 4:01 PM, Marcel Kinard 
> wrote:
> >
> >> FYI, I am getting the following warning when I do "npm install
> cordova@rc
> >> ":
> >>
> >> npm WARN engine connect@1.8.5: wanted: {"node":">= 0.4.1 < 0.7.0"}
> >> (current: {"node":"0.10.31","npm":"1.4.23"})
> >>
> >> This is a devDependency in cordova-js, which I didn't change. If folks
> >> want this dependency changed to get rid of the warning, then it will
> mean
> >> respinning this tools release.
>
>


-- 
Carlos Santana

Re: [Vote] 3.6.3 Cadence Release

[Carlos Santana]

Marcel forgot to mentioned that I updated to latest npm via "npm update -g
npm" newer than the one in v0.10.31, when I was playing with npm shrinkwrap.

/Users/csantana23

$ node -v

v0.10.31

/Users/csantana23

$ npm -v

1.4.27


which should not confuse you with 1.4.28 which is not latest but is tag
v1.4-next in npmjs.org

I know npm will grow on you with time :-)



On Tue, Sep 16, 2014 at 2:38 PM, Marcel Kinard  wrote:

> I think the esprima-fb error is a bug in npm, which is installing the
> wrong version of that module.
>
> $ vi
> /Users/marcelk/Developer/apache/cordova-lib/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb/package.json
>   "version": "6001.1.0-dev-harmony-fb",
>
> $ vi
> /Users/marcelk/Developer/apache/cordova-lib/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/package.json
>   "dependencies": {
> "esprima-fb": "^3001.1.0-dev-harmony-fb"
>   },
>
> When running "npm shrinkwrap" it will fail if the version installed in
> node_modules differs from what is specified in the parent package.json.
> That is what the error means.
>
> Not sure why this is happening, but bumping browserify to a recent version
> (which gets rid of the derequire dependency) in cordova-js clears it up.
>
> Hmm, why does cordova-lib have a dependency on cordova-js?
>
> On Sep 16, 2014, at 9:02 AM, Marcel Kinard  wrote:
>
> > I'm getting the same error on esprima-fb when updating the shrinkwrap.
> I'll update the browserify dependency, update the shrinkwrap, build a new
> tools snapshot, publish it to npm as an rc for final testing, and post it
> for a 24-hour vote.
> >
> > On Sep 15, 2014, at 11:30 PM, Carlos Santana 
> wrote:
> >
> >> I was trying myself to generate a npm-shrinkwrap.json and got an error
> >> associated with the version of browserfy included in cordova-js which is
> >> included in cordova-lib:-)
> >> 0 info it worked if it ends with ok
> >> 1 verbose cli [ 'node',
> >> 1 verbose cli   '/Users/csantana23/.nvm/v0.10.31/bin/npm',
> >> 1 verbose cli   'shrinkwrap' ]
> >> 2 info using npm@1.4.27
> >> 3 info using node@v0.10.31
> >> 4 error Error: Problems were encountered
> >> 4 error Please correct and try again.
> >> 4 error invalid: esprima-fb@6001.1.0-dev-harmony-fb
> >>
> /Users/csantana23/Documents/SWG/git/cordova/cordova-cli/node_modules/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb
> >> 4 erro
> >>
> >> It looks we are using a 3 months old version 3.46
> >> Latest is 5.11.2 https://www.npmjs.org/package/browserify
> >>
> >> If we update cordova-js dependency for browserfy from 3.46 to 5.11.2 the
> >> npm shrinkwrap command doesn't fail
>
>


-- 
Carlos Santana

Re: NFC and IOS

[Shazron]

No :/ You just log in from time to time and see your bug -- it should
reference the original highlighted in yellow. There the text will show the
status "Open" or "Closed" for the original bug.

On Tuesday, September 16, 2014, Don Coleman  wrote:

> Apple closed my by "Add NFC APIs" bug report as a duplicate.
> "Engineering has determined that your bug report (18295114) is a duplicate
> of another issue (18337769) and will be closed."
>
> Is there any way to see the status or watch an Apple bug I didn't report?
>
> On Tue, Sep 16, 2014 at 3:31 PM, Kerri Shotts  > wrote:
>
> > Buses? What are those? ;)
> >
> > I suspect that the API is still baking and will be opened up to everyone
> > in a later release (probably iOS 9), but that is just a (hopeful) guess
> on
> > my part.
> >
> > Sent from my phone.
> >
> > ___
> > Kerri Shotts
> > photoKandy Studios, LLC
> >
> > On the Web: http://www.photokandy.com/
> >
> > Social Media:
> >   Twitter: @photokandy, http://twitter.com/photokandy
> >   Tumblr: http://photokandy.tumblr.com/
> >   Github: https://github.com/kerrishotts
> >
> https://github.com/organizations/photokandyStudios
> >   CoderWall: https://coderwall.com/kerrishotts
> >
> >
> > > On Sep 16, 2014, at 14:18, Joe Bowser  > wrote:
> > >
> > > As we've seen with Apple Maps, iPhone users don't ride the bus.
> > > On Sep 16, 2014 12:16 PM, "julio cesar sanchez" <
> jcesarmob...@gmail.com >
> > > wrote:
> > >
> > >> Bad news
> > >>
> > >>
> > >>
> >
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay
> > >> <
> > >>
> >
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay/?mod=rss_Technology&utm_source=dlvr.it&utm_medium=twitter
> > >>
> >
>

Re: NFC and IOS

[Don Coleman]

Apple closed my by "Add NFC APIs" bug report as a duplicate.
"Engineering has determined that your bug report (18295114) is a duplicate
of another issue (18337769) and will be closed."

Is there any way to see the status or watch an Apple bug I didn't report?

On Tue, Sep 16, 2014 at 3:31 PM, Kerri Shotts  wrote:

> Buses? What are those? ;)
>
> I suspect that the API is still baking and will be opened up to everyone
> in a later release (probably iOS 9), but that is just a (hopeful) guess on
> my part.
>
> Sent from my phone.
>
> ___
> Kerri Shotts
> photoKandy Studios, LLC
>
> On the Web: http://www.photokandy.com/
>
> Social Media:
>   Twitter: @photokandy, http://twitter.com/photokandy
>   Tumblr: http://photokandy.tumblr.com/
>   Github: https://github.com/kerrishotts
> https://github.com/organizations/photokandyStudios
>   CoderWall: https://coderwall.com/kerrishotts
>
>
> > On Sep 16, 2014, at 14:18, Joe Bowser  wrote:
> >
> > As we've seen with Apple Maps, iPhone users don't ride the bus.
> > On Sep 16, 2014 12:16 PM, "julio cesar sanchez" 
> > wrote:
> >
> >> Bad news
> >>
> >>
> >>
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay
> >> <
> >>
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay/?mod=rss_Technology&utm_source=dlvr.it&utm_medium=twitter
> >>
>

[GitHub] cordova-plugin-splashscreen pull request: CB-7204 Fixed race condi...

[shazron]

Github user shazron commented on the pull request:


https://github.com/apache/cordova-plugin-splashscreen/pull/21#issuecomment-55830716
  
Not sure what you meant exactly by your last comment. So is my proposed fix 
would be the better way in your opinion?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cordova-plugin-statusbar pull request: ios 8 landscape issue

[shazron]

Github user shazron commented on the pull request:


https://github.com/apache/cordova-plugin-statusbar/pull/15#issuecomment-55830633
  
Patched: 
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-statusbar.git;h=921dacc
please close this PR. thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cordova-plugin-statusbar pull request: ios 8 landscape issue

[shazron]

Github user shazron commented on the pull request:


https://github.com/apache/cordova-plugin-statusbar/pull/15#issuecomment-55829982
  
https://issues.apache.org/jira/browse/CB-7549



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

Sorry I'm not following exactly what you mean. Do you mean cordova-lib instead 
of cordova-cli?

I also don't expect devDependencies to get installed when I do "npm -g install 
cordova@rc".

cordova-js has the devDependency on connect, and does not have a shrinkwrap. 
cordova-lib has a dependency on cordova-js, but does have a shrinkwrap. When I 
generate the shrinkwrap in cordova-lib, all of the devDependencies in 
cordova-js are appearing in the cordova-lib shrinkwrap. That seems to be where 
it starts to go wrong. 

cd cordova-lib
rm -r node_modules
rm npm-shrinkwrap
npm install
npm shrinkwrap

...and I see the cordova-js devDependencies in the cordova-lib shrinkwrap. 
That's wrong, correct?

It shouldn't matter if I had done an "npm link cordova-js" inside of 
cordova-lib, correct? 

I'm trying to figure out if I'm doing something wrong, or if the shrinkwrap 
command is misbehaving.

On Sep 16, 2014, at 4:07 PM, Andrew Grieve  wrote:

> You shouldn't be seeing devDependencies show up in cordova. I'd double make
> sure that if you:
> 
> cd cordova-cli
> rm -r node_modules
> rm npm-shrinkwrap.json
> npm install
> npm shrinkwrap
> 
> 
> that you end up with an npm-shrinkwrap.json that includes the devDependency.
> 
> 
> On Tue, Sep 16, 2014 at 4:01 PM, Marcel Kinard  wrote:
> 
>> FYI, I am getting the following warning when I do "npm install cordova@rc
>> ":
>> 
>> npm WARN engine connect@1.8.5: wanted: {"node":">= 0.4.1 < 0.7.0"}
>> (current: {"node":"0.10.31","npm":"1.4.23"})
>> 
>> This is a devDependency in cordova-js, which I didn't change. If folks
>> want this dependency changed to get rid of the warning, then it will mean
>> respinning this tools release.

[GitHub] cordova-docs pull request: CB-7565 add debugging guide for iOS wit...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/237#issuecomment-55810732
  
Patch integrated (commits squashed). However, the output is a bit weird for 
the "Xcode Debugging" link (not your fault, it's joDoc's). Through it's own 
magic, it split the link to only link to the "Xcode" text, but not the whole 
"Xcode Debugging". "Debugging" links to ... itself.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Vote] Tools Release 3.6.3-0.2.12

[Andrew Grieve]

You shouldn't be seeing devDependencies show up in cordova. I'd double make
sure that if you:

cd cordova-cli
rm -r node_modules
rm npm-shrinkwrap.json
npm install
npm shrinkwrap


that you end up with an npm-shrinkwrap.json that includes the devDependency.


On Tue, Sep 16, 2014 at 4:01 PM, Marcel Kinard  wrote:

> FYI, I am getting the following warning when I do "npm install cordova@rc
> ":
>
> npm WARN engine connect@1.8.5: wanted: {"node":">= 0.4.1 < 0.7.0"}
> (current: {"node":"0.10.31","npm":"1.4.23"})
>
> This is a devDependency in cordova-js, which I didn't change. If folks
> want this dependency changed to get rid of the warning, then it will mean
> respinning this tools release.

[GitHub] cordova-docs pull request: CB-7565 add debugging guide for iOS wit...

[eymorale]

GitHub user eymorale opened a pull request:

https://github.com/apache/cordova-docs/pull/237

CB-7565 add debugging guide for iOS with references to xcode and safari web 
inspector



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/eymorale/cordova-docs CB-7565

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-docs/pull/237.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #237


commit 54de15e7822180c02e57564579fbede752687f47
Author: Edna Morales 
Date:   2014-09-16T19:55:12Z

CB-7565 add debugging guide for iOS with xcode and safari web inspector

commit 27d01f1f0129ca885932da992c43bbe8874756c9
Author: Edna Morales 
Date:   2014-09-16T20:01:28Z

CB-7565 mixmatch typo in iOS debugging guide




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

FYI, I am getting the following warning when I do "npm install cordova@rc":

npm WARN engine connect@1.8.5: wanted: {"node":">= 0.4.1 < 0.7.0"} (current: 
{"node":"0.10.31","npm":"1.4.23"})

This is a devDependency in cordova-js, which I didn't change. If folks want 
this dependency changed to get rid of the warning, then it will mean respinning 
this tools release.

Re: [Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

Typo, should say: "Ran coho verify-archive over the relevant repos"

On Sep 16, 2014, at 3:51 PM, Marcel Kinard  wrote:

> * Ran coho audit-license-headers over the relevant repos

[Vote] Tools Release 3.6.3-0.2.12

[Marcel Kinard]

Please review and vote on this Tools Release.

This tools release addresses an issue with the npm-shrinkwrap that occurred 
while publishing the 3.6.3 platforms. The cordova-js dependency on browserify 
was updated, and that was cascaded up the dependency tree through cordova-lib 
and cordova-cli. And the dependency in cordova-cli on cordova-lib was updated. 
Other than that, there is no new content versus the tools in the 3.6.3 
platforms release. The change to cordova-js was only the dependency on 
browserify which is not needed in the platforms, so the cordova.js in the 
platforms was not updated and re-tagged.

I published these tools to npm with the "rc" tag, so you can test it by running 
"npm -g install cordova@rc". You should get the package (js, lib, plugman, cli) 
versions as listed below. And "platform add" should get version 3.6.3 of the 
platforms.

Release issue: https://issues.apache.org/jira/browse/CB-7383

They have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-7383/

The packages were published from their corresponding git tags:
cordova-js: 3.6.4 (7d593689ee)
cordova-lib: 0.21.12 (6353bdfa08)
cordova-plugman: 0.22.9 (949cd5e767)
cordova-cli: 3.6.3-0.2.12 (e305584f6c)

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 24 hours. The voting period is shorter than 
usual due to the many reviews which have already been done.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Installed from npm and built an Android app with all the correct module 
versions
* Created from a branch that limits content other than the previous 3.6.3 
platform release

[GitHub] cordova-plugin-geolocation pull request: added simple geolocation

[jbeuckm]

GitHub user jbeuckm opened a pull request:

https://github.com/apache/cordova-plugin-geolocation/pull/26

added simple geolocation

Addresses CB-7563

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbeuckm/cordova-plugin-geolocation CB-7563

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-geolocation/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #26


commit 08f3d9c5a639091826492eb2eb0db38c22bab458
Author: joe 
Date:   2014-09-16T19:18:43Z

added simple geolocation




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: NFC and IOS

[Kerri Shotts]

Buses? What are those? ;)

I suspect that the API is still baking and will be opened up to everyone in a 
later release (probably iOS 9), but that is just a (hopeful) guess on my part. 

Sent from my phone. 

___
Kerri Shotts
photoKandy Studios, LLC

On the Web: http://www.photokandy.com/

Social Media:
  Twitter: @photokandy, http://twitter.com/photokandy
  Tumblr: http://photokandy.tumblr.com/
  Github: https://github.com/kerrishotts
https://github.com/organizations/photokandyStudios
  CoderWall: https://coderwall.com/kerrishotts


> On Sep 16, 2014, at 14:18, Joe Bowser  wrote:
> 
> As we've seen with Apple Maps, iPhone users don't ride the bus.
> On Sep 16, 2014 12:16 PM, "julio cesar sanchez" 
> wrote:
> 
>> Bad news
>> 
>> 
>> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay
>> <
>> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay/?mod=rss_Technology&utm_source=dlvr.it&utm_medium=twitter
>> 

Re: NFC and IOS

[Joe Bowser]

As we've seen with Apple Maps, iPhone users don't ride the bus.
On Sep 16, 2014 12:16 PM, "julio cesar sanchez" 
wrote:

> Bad news
>
>
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay
> <
> http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay/?mod=rss_Technology&utm_source=dlvr.it&utm_medium=twitter
> >
>

Re: NFC and IOS

[julio cesar sanchez]

Bad news

http://blogs.wsj.com/digits/2014/09/16/iphones-nfc-tech-will-only-work-with-apple-pay

Re: [Vote] 3.6.3 Cadence Release

[Marcel Kinard]

I think the esprima-fb error is a bug in npm, which is installing the wrong 
version of that module.

$ vi 
/Users/marcelk/Developer/apache/cordova-lib/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb/package.json
  "version": "6001.1.0-dev-harmony-fb",

$ vi 
/Users/marcelk/Developer/apache/cordova-lib/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/package.json
  "dependencies": {
"esprima-fb": "^3001.1.0-dev-harmony-fb"
  },

When running "npm shrinkwrap" it will fail if the version installed in 
node_modules differs from what is specified in the parent package.json. That is 
what the error means.

Not sure why this is happening, but bumping browserify to a recent version 
(which gets rid of the derequire dependency) in cordova-js clears it up.

Hmm, why does cordova-lib have a dependency on cordova-js?

On Sep 16, 2014, at 9:02 AM, Marcel Kinard  wrote:

> I'm getting the same error on esprima-fb when updating the shrinkwrap. I'll 
> update the browserify dependency, update the shrinkwrap, build a new tools 
> snapshot, publish it to npm as an rc for final testing, and post it for a 
> 24-hour vote. 
> 
> On Sep 15, 2014, at 11:30 PM, Carlos Santana  wrote:
> 
>> I was trying myself to generate a npm-shrinkwrap.json and got an error
>> associated with the version of browserfy included in cordova-js which is
>> included in cordova-lib:-)
>> 0 info it worked if it ends with ok
>> 1 verbose cli [ 'node',
>> 1 verbose cli   '/Users/csantana23/.nvm/v0.10.31/bin/npm',
>> 1 verbose cli   'shrinkwrap' ]
>> 2 info using npm@1.4.27
>> 3 info using node@v0.10.31
>> 4 error Error: Problems were encountered
>> 4 error Please correct and try again.
>> 4 error invalid: esprima-fb@6001.1.0-dev-harmony-fb
>> /Users/csantana23/Documents/SWG/git/cordova/cordova-cli/node_modules/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb
>> 4 erro
>> 
>> It looks we are using a 3 months old version 3.46
>> Latest is 5.11.2 https://www.npmjs.org/package/browserify
>> 
>> If we update cordova-js dependency for browserfy from 3.46 to 5.11.2 the
>> npm shrinkwrap command doesn't fail

Re: CB-5921

[Shazron]

Thanks Erik,
I'll take a look soon. As long as it addresses the points I've been making
in the issue (wrt plugins) it would be fine -- the target is by 4.0 release
I would think for using workspaces. Yes, Swift is only supported with iOS 7
and up, so a Swift developed plugin needs to have as an engine tag value
the Cordova release that supports iOS 7 and up.

We haven't broached the subject of dropping iOS 6 support, but generally we
do only want to support the current and previous iOS release -- but we'll
let the list know if there are any concerns.

On Tue, Sep 16, 2014 at 9:43 AM, julio cesar sanchez  wrote:

> But you can't use swift if you support iOS 6, and cordova still supports
> iOS 6
>

Re: [Vote] 3.6.3 Cadence Release

[Archana Naik]

No worries Marcel. Appreciate you doing this for us. Looking forward to
next rc.

Archana

On Tue, Sep 16, 2014 at 6:02 AM, Marcel Kinard  wrote:

> Since the platforms don't have a shrinkwrap, those don't need to be
> updated, so we can leave them as-is. So just the tools need to be updated.
>
> I'm getting the same error on esprima-fb when updating the shrinkwrap.
> I'll update the browserify dependency, update the shrinkwrap, build a new
> tools snapshot, publish it to npm as an rc for final testing, and post it
> for a 24-hour vote.
>
> I don't think we need 72 hours given the number of reviews that 3.6.x has
> already had so far.
>
> Archana / Bryan / Sergey, my apologies on the reviews/votes you've done on
> artifacts which didn't completely publish. I'll test this last one in npm
> before putting it up for a vote.
>
> On Sep 15, 2014, at 11:30 PM, Carlos Santana  wrote:
>
> > I was trying myself to generate a npm-shrinkwrap.json and got an error
> > associated with the version of browserfy included in cordova-js which is
> > included in cordova-lib:-)
> > 0 info it worked if it ends with ok
> > 1 verbose cli [ 'node',
> > 1 verbose cli   '/Users/csantana23/.nvm/v0.10.31/bin/npm',
> > 1 verbose cli   'shrinkwrap' ]
> > 2 info using npm@1.4.27
> > 3 info using node@v0.10.31
> > 4 error Error: Problems were encountered
> > 4 error Please correct and try again.
> > 4 error invalid: esprima-fb@6001.1.0-dev-harmony-fb
> >
> /Users/csantana23/Documents/SWG/git/cordova/cordova-cli/node_modules/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb
> > 4 erro
> >
> > It looks we are using a 3 months old version 3.46
> > Latest is 5.11.2 https://www.npmjs.org/package/browserify
> >
> > If we update cordova-js dependency for browserfy from 3.46 to 5.11.2 the
> > npm shrinkwrap command doesn't fail
>

Re: CB-5921

[julio cesar sanchez]

But you can't use swift if you support iOS 6, and cordova still supports
iOS 6

[GitHub] cordova-plugin-dialogs pull request: CB-7538 Android beep thread f...

[dpeacock]

Github user dpeacock closed the pull request at:

https://github.com/apache/cordova-plugin-dialogs/pull/33


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Vote] 3.6.3 Cadence Release

[Marcel Kinard]

Since the platforms don't have a shrinkwrap, those don't need to be updated, so 
we can leave them as-is. So just the tools need to be updated.

I'm getting the same error on esprima-fb when updating the shrinkwrap. I'll 
update the browserify dependency, update the shrinkwrap, build a new tools 
snapshot, publish it to npm as an rc for final testing, and post it for a 
24-hour vote. 

I don't think we need 72 hours given the number of reviews that 3.6.x has 
already had so far.

Archana / Bryan / Sergey, my apologies on the reviews/votes you've done on 
artifacts which didn't completely publish. I'll test this last one in npm 
before putting it up for a vote.

On Sep 15, 2014, at 11:30 PM, Carlos Santana  wrote:

> I was trying myself to generate a npm-shrinkwrap.json and got an error
> associated with the version of browserfy included in cordova-js which is
> included in cordova-lib:-)
> 0 info it worked if it ends with ok
> 1 verbose cli [ 'node',
> 1 verbose cli   '/Users/csantana23/.nvm/v0.10.31/bin/npm',
> 1 verbose cli   'shrinkwrap' ]
> 2 info using npm@1.4.27
> 3 info using node@v0.10.31
> 4 error Error: Problems were encountered
> 4 error Please correct and try again.
> 4 error invalid: esprima-fb@6001.1.0-dev-harmony-fb
> /Users/csantana23/Documents/SWG/git/cordova/cordova-cli/node_modules/cordova-lib/node_modules/cordova-js/node_modules/browserify/node_modules/derequire/node_modules/esprima-fb
> 4 erro
> 
> It looks we are using a 3 months old version 3.46
> Latest is 5.11.2 https://www.npmjs.org/package/browserify
> 
> If we update cordova-js dependency for browserfy from 3.46 to 5.11.2 the
> npm shrinkwrap command doesn't fail

Re: [Vote] 3.6.3 Cadence Release

[Marcel Kinard]

Agreed, especially in this situation where esprima-fb is no longer valid. 
Except that we don't have a defined test period during which to run with a 
specific shrinkwrap. I'll put together a proposal and send it out for review.

On Sep 15, 2014, at 11:28 PM, Carlos Santana  wrote:

> We should always update shrinkwrap.json before going thru test, that way if
> there is a dependency down the chain (i.e. ALL the chain) that got updated
> we can pick up the new version and everybody test the same bits.

Re: CB-5921

[Erik Jan de Wit]

Ultimate goal is to enable swift as a language to create plugins with

On 16 Sep,2014, at 14:43 , Erik Jan de Wit  wrote:

> Hi,
> 
> I’ve started to work on https://issues.apache.org/jira/browse/CB-5921 and 
> create a PR https://github.com/apache/cordova-ios/pull/104 that will generate 
> a workspace instead of a subproject. Next step is to look how to integrate 
> this with cli and maybe change how cli does changes to the project ( use 
> xconfig files instead of changing pbxpoj )
> 
> Cheers,
>   Erik Jan

Re: cordova push plugin release

[Erik Jan de Wit]

Ultimate goal is to enable swift as a language to create plugins with

On 16 Sep,2014, at 11:41 , Erik Jan de Wit  wrote:

> Hi all,
> 
> After testing we are happy to announce that the 1.0.1 version of the cordova 
> push plugin has been released. Thanks to everyone for testing and making this 
> release happen. The reason for this point release was an error in the android 
> dependencies of the plugin making it unusable.
> 
> Happy coding,
>   Erik Jan

CB-5921

[Erik Jan de Wit]

Hi,

I’ve started to work on https://issues.apache.org/jira/browse/CB-5921 and 
create a PR https://github.com/apache/cordova-ios/pull/104 that will generate a 
workspace instead of a subproject. Next step is to look how to integrate this 
with cli and maybe change how cli does changes to the project ( use xconfig 
files instead of changing pbxpoj )

Cheers,
Erik Jan

[GitHub] cordova-ios pull request: generates a workspace instead of subproj...

[edewit]

GitHub user edewit opened a pull request:

https://github.com/apache/cordova-ios/pull/104

generates a workspace instead of subproject



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/edewit/cordova-ios workspace

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-ios/pull/104.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #104


commit 9b1510768dbb6f74b4c7e95a307ba237234d893e
Author: Erik Jan de Wit 
Date:   2014-09-16T12:24:09Z

generates a workspace instead of subproject




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

cordova push plugin release

[Erik Jan de Wit]

Hi all,

After testing we are happy to announce that the 1.0.1 version of the cordova 
push plugin has been released. Thanks to everyone for testing and making this 
release happen. The reason for this point release was an error in the android 
dependencies of the plugin making it unusable.

Happy coding,
Erik Jan

[GitHub] cordova-plugin-inappbrowser pull request: Send 'Activity not found...

[rromerogar]

GitHub user rromerogar opened a pull request:

https://github.com/apache/cordova-plugin-inappbrowser/pull/62

Send 'Activity not found' as an error result to Javascript

When opened an URI with window.open(url,'_system') and throws a "Not 
Activity found", event 'errorloading' it's not fired. With this request will 
resolve this.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rromerogar/cordova-plugin-inappbrowser master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-inappbrowser/pull/62.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #62


commit 2e00cc549a6912739263e3f01922656aff74a14a
Author: rromerogar 
Date:   2014-09-16T08:39:41Z

Send 'Activity not found' as an error result to Javascript




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cordova-plugin-splashscreen pull request: CB-7204 Fixed race condi...

[kant2002]

Github user kant2002 commented on the pull request:


https://github.com/apache/cordova-plugin-splashscreen/pull/21#issuecomment-55703938
  
Sorry, I reread your comment and realize that my earlier comment is 
probably off-topic.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---