[GitHub] cordova-plugin-camera pull request: [Android] fix: support lollipo...

[SecuriTeam]

GitHub user SecuriTeam opened a pull request:

https://github.com/apache/cordova-plugin-camera/pull/93

[Android] fix: support lollipop and earlier android versions to return a 
file path from uri regardless of file type.

I've only tested this on Android versions:
LG Optimus L3 II - 4.1.1 - API 16
Samsung Galaxy S3 - 4.2.2 - API 17
HTC Evo - 4.3 - API 18
Nexus 4 - 5.0.0 - API 21
on Genymotion emulator.
and Galaxy Note 3 - 5.0.0 - API 21 on my actual phone.

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

$ git pull https://github.com/SecuriTeam/cordova-plugin-camera master

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

https://github.com/apache/cordova-plugin-camera/pull/93.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 #93


commit 4a1cb9fb7a12745a095b6cdfffef853c6c16fb0f
Author: Shadi Habbal 
Date:   2015-05-07T08:04:15Z

[Android] fix: support lollipop and earlier android versions to return a 
file path from uri regardless of file type.




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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-file-transfer pull request: Fix NoSuchMethodExcepti...

[mkyung]

Github user mkyung commented on the pull request:


https://github.com/apache/cordova-plugin-file-transfer/pull/68#issuecomment-99780130
  
+1 This fix is working. Please merge it ASAP


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-inappbrowser pull request: CB-3750: Add loading spi...

[syndbg]

Github user syndbg commented on the pull request:


https://github.com/apache/cordova-plugin-inappbrowser/pull/89#issuecomment-99841604
  
I suggest that this is a bit more flexible.

Don't force the color and spinner to be always visible.

Instead introduce two options ex. `spinnerColor` and `spinnerHidden` 


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[brodybits]

Github user brodybits commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99847116
  
> @brodybits follow these steps:

as documented in https://github.com/apache/cordova-plugin-test-framework. 
Could add a reference to README.md in the plugin for those who may be 
unfamiliar. Thanks @vladimir-kotikov.

> It looks like these changes brought new test failures on wp8:
> https://issues.apache.org/jira/browse/CB-8968

If we would restore the old code in `JsonHelper.Serialize` in 
`template/cordovalib/JSON/JsonHelper.cs` then the problem in CB-8968 goes away. 
Then:

Using `JsonConvert.SerializeObject` from `Newtonsoft.Json` in 
cordova-plugin-file *is working OK in the test*:

```diff
--- a/src/wp/File.cs
+++ b/src/wp/File.cs
@@ -22,7 +22,9 @@
 using System.Text;
 using System.Windows;
 using System.Windows.Resources;
+
 using WPCordovaClassLib.Cordova.JSON;
+using Newtonsoft.Json;
 
 namespace WPCordovaClassLib.Cordova.Commands
 {
@@ -771,7 +773,7 @@ public void readAsText(string options)
 // JIRA: https://issues.apache.org/jira/browse/CB-8792
 // Need to perform additional serialization here because 
NativeExecution is always trying
 // to do JSON.parse() on command result. This leads to 
issue when trying to read JSON files
-var resultText = JsonHelper.Serialize(text);
+var resultText = JsonConvert.SerializeObject(text);
 DispatchCommandResult(new 
PluginResult(PluginResult.Status.OK, resultText), callbackId);
 }
 catch (Exception ex)
```

Using `JsonConvert.SerializeObject` from `Newtonsoft.Json` in 
`template/cordovalib/ScriptCallback.cs` is *working OK in the 
cordova-plugin-file test*:

```diff
--- a/template/cordovalib/ScriptCallback.cs
+++ b/template/cordovalib/ScriptCallback.cs
@@ -25,6 +25,8 @@
 using WPCordovaClassLib.Cordova.JSON;
 using System.Diagnostics;
 
+using Newtonsoft.Json;
+
 namespace WPCordovaClassLib.Cordova
 {
 /// 
@@ -65,7 +67,7 @@ public ScriptCallback(string function, string id, object 
msg, object value)
 this.ScriptName = function;
 
 String arg = String.Format("{{\"id\": {0}, \"msg\": {1}, 
\"value\": {2}}}",
- JsonHelper.Serialize(id), JsonHelper.Serialize(msg), 
JsonHelper.Serialize(value));
+ JsonConvert.SerializeObject(id), 
JsonConvert.SerializeObject(msg), JsonConvert.SerializeObject(value));
 
 this.Args = new string[] { arg };
 }
```

Using `JsonConvert.SerializeObject` from `Newtonsoft.Json` in 
`template/cordovalib/CordovaCommandCall.cs` gave me a problem with 
`file.spec.83` (blob test) the first time, then was passing the 
cordova-plugin-file tests when I tried it again (should be OK).

Using `JsonConvert.SerializeObject` from `Newtonsoft.Json` in 
`template/cordovalib/PluginResult.cs` gives me the errors as described in 
CB-8968.

Wondering if any other Apache Cordova or major third-party plugins would be 
affected as well.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Buildbot: buildslave cordova-win8-slave was lost

[buildbot]

The Buildbot working for 'ASF Buildbot'
has noticed that the buildslave named cordova-win8-slave went away

It last disconnected at Thu May  7 13:05:06 2015 (buildmaster-local time)

The admin on record (as reported by BUILDSLAVE:info/admin)
was 'None'.

Sincerely,
 The Buildbot
 http://ci.apache.org/

http://ci.apache.org/buildslaves/cordova-win8-slave

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Buildbot: buildslave cordova-common-slave was lost

[buildbot]

The Buildbot working for 'ASF Buildbot'
has noticed that the buildslave named cordova-common-slave went away

It last disconnected at Thu May  7 13:05:06 2015 (buildmaster-local time)

The admin on record (as reported by BUILDSLAVE:info/admin)
was 'None'.

Sincerely,
 The Buildbot
 http://ci.apache.org/

http://ci.apache.org/buildslaves/cordova-common-slave

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Buildbot: buildslave cordova-blackberry-slave was lost

[buildbot]

The Buildbot working for 'ASF Buildbot'
has noticed that the buildslave named cordova-blackberry-slave went away

It last disconnected at Thu May  7 13:05:06 2015 (buildmaster-local time)

The admin on record (as reported by BUILDSLAVE:info/admin)
was 'None'.

Sincerely,
 The Buildbot
 http://ci.apache.org/

http://ci.apache.org/buildslaves/cordova-blackberry-slave

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Buildbot: buildslave cordova-android-slave was lost

[buildbot]

The Buildbot working for 'ASF Buildbot'
has noticed that the buildslave named cordova-android-slave went away

It last disconnected at Thu May  7 13:05:06 2015 (buildmaster-local time)

The admin on record (as reported by BUILDSLAVE:info/admin)
was 'None'.

Sincerely,
 The Buildbot
 http://ci.apache.org/

http://ci.apache.org/buildslaves/cordova-android-slave

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8752 Adds docs for hooks functionali...

[sgrebnov]

GitHub user sgrebnov opened a pull request:

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

CB-8752 Adds docs for hooks functionality

1. Moving hooks documentation to docs as this is general and not 
hello-world app specific

https://github.com/apache/cordova-app-hello-world/blob/master/hooks/README.md
2. Added Sample Usage section w/ end-to-end example



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

$ git pull https://github.com/MSOpenTech/cordova-docs CB-8752

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

https://github.com/apache/cordova-docs/pull/285.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 #285


commit ad42d959a078479e2fbaf9d519bca2f124de3e67
Author: sgrebnov 
Date:   2015-05-02T00:36:01Z

CB-8752 Adds docs for hooks functionality




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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-8752 Adds docs for hooks functionali...

[sgrebnov]

Github user sgrebnov commented on the pull request:

https://github.com/apache/cordova-docs/pull/285#issuecomment-99873253
  
The following places must be updated to point to the docs after this is 
merged and released:

https://github.com/apache/cordova-app-hello-world/blob/master/hooks/README.md
https://github.com/apache/cordova-cli/#hooks-1


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Cordova Plugins with Symlinks

[Andrew Grieve]

Could we fix our un-tarring logic to create symlinks on windows?

On Wed, May 6, 2015 at 2:39 PM, Chuck Lantz  wrote:

> Yeah that was one of the alternatives I was thinking about as a part of
> that pre-publish step I mentioned. Really, you'd need to either:
>
> 1. Provide a general mechanism for all symlinks using a metadata file
> a. Prep-publish: Run through and find paths to symlinks (which is
> easy to do with node), store in a json file with the plugin
> b. After Platform Add / Plugin Add, or just Before Compile: Use
> the metadata file to generate the symlinks if OS = OSX or Linux
>
> 2. Provide a specific mechanism to deal with frameworks
> a. Pre-publish: Find custom frameworks. (Which you can actually do
> using plugin.xml), tgz them
> b. After Platform Add / Plugin Add, or just Before Compile: Expand
> framework tgz if found
>
> (a) could be done via npm but (b) really has to be done via a Cordova hook
> or be inherent to the iOS platform.
>
> Maybe the thing to do is to develop these hooks and add them to the
> default template for plugins and in addition to the docs.  #1 is likely a
> bit more robust.
>
> -Chuck
>
> -Original Message-
> From: Josh Soref [mailto:jso...@blackberry.com]
> Sent: Wednesday, May 6, 2015 11:05 AM
> To: dev@cordova.apache.org
> Subject: RE: Cordova Plugins with Symlinks
>
> It should be possible for our build system to convert some metadata into
> symlinks which are fed to whatever build thing actually requires them, but
> allows us to not have genuine symlinks in the working directory.
>
> The BlackBerry 10 project copies all the files it wants to package over
> into another directory, other platforms should be able to do similar.
>
> > -Original Message-
> > From: Shazron [mailto:shaz...@gmail.com]
> > Sent: Wednesday, May 06, 2015 1:23 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Cordova Plugins with Symlinks
> >
> > Ordinarily I agree with Jesse's sentiment about not using symlinks but
> > that is just the reality for .frameworks.
> >
> > That being said, I don't think we should do anything extra for authors
> > _but_ instead provide a middle ground that you mentioned "provide
> > guidance to plugin authors to work around this problem" and even as a
> > pre-publish (or analysis) step that checks whether this might be a
> > problem, and warns them.
> >
> > On Wed, May 6, 2015 at 9:54 AM, Chuck Lantz 
> > wrote:
> > > Yeah, I agree symlinks should be avoided, but what Ally highlighted
> below
> > is that it is required in this case. ("@Ian Absolutely required. Not
> just for
> > Facebook, but all .framework files.") Given that statement, it seems
> that in
> > this case we need to have some sort of solution to remediate the problem
> > does it not?
> > >
> > > -Chuck
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Wednesday, May 6, 2015 9:16 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: Cordova Plugins with Symlinks
> > >
> > > I think in this case we should be not be using symlinks. All of our
> output
> > project types support adding a reference to a file or folder, we should
> > leverage this directly.
> > > Of course, this could possibly lead to forward vs back slash issues,
> but
> > should be easier than running hook hacks.
> > > At least I think we should explore this way.
> > >
> > >
> > >> On May 6, 2015, at 7:53 AM, Chuck Lantz  wrote:
> > >>
> > >> Hey folks,
> > >>
> > >> So I’ve started to see some issues come up with certain Cordova
> > plugins when devs are mixing a Windows and OSX environment together
> > when developing an app. Digging into it a bit, it looks like root cause
> is that
> > there are some situations where iOS plugin implementations with custom
> > frameworks that require symlinks - as described in the thread below.
> > >>
> > >> In addition to the situation mentioned in the thread, there's a
> second one
> > worth calling out: installing a plugin with symlinks on Windows on the
> NTFS
> > file system results in the symlinks becoming files.
> > >>
> > >> The workaround described in this thread (zipping as a tarball) helps
> when
> > plugin installs happen on OSX, but it doesn't resolve the problem with
> NTFS.
> > If a development team is split between OSX and Windows machines, the
> > plugin will appear broken on iOS if it was committed/checked in/copied
> from
> > Windows. If, on the other hand, the plugin is added from OSX, it will
> work -
> > the end result is the behavior seems "glitchy" and it is not at all
> obvious what
> > happened when things go wrong.
> > >>
> > >> I came up with a hook that fixes these symlinks since the files that
> > >> are generated do contain the relative path to the underlying folder
> > >> – but it is admittedly a bit of a hack since it attempts to handle
> > >> any arbitrary plugin:
> > >>
> https://github.com/Chuxel/taco-tricks/tree/master/ios-plugin-symlink-f
> > >> ix
> > >>
>

RE: Cordova Plugins with Symlinks

[Chuck Lantz]

Possibly using junctions. 

Actual symlinks require administrator privileges and there's no "sudo" like 
command which is why they're not used frequently.  You can create "folder 
junctions" (via mklink) without admin privs which would technically meet the 
need here since these are folder symlinks. 

One issue with junctions, however, is junctions look like folders when zipped 
or committed to a Git repo, so basically you just duplicate all the files. 
However, as long as frameworks will work with the contents duplicated rather 
than symlink'd, it make be an acceptable workaround.  Need to validate.

-Chuck

-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, May 7, 2015 6:55 AM
To: dev
Subject: Re: Cordova Plugins with Symlinks

Could we fix our un-tarring logic to create symlinks on windows?

On Wed, May 6, 2015 at 2:39 PM, Chuck Lantz  wrote:

> Yeah that was one of the alternatives I was thinking about as a part 
> of that pre-publish step I mentioned. Really, you'd need to either:
>
> 1. Provide a general mechanism for all symlinks using a metadata file
> a. Prep-publish: Run through and find paths to symlinks (which 
> is easy to do with node), store in a json file with the plugin
> b. After Platform Add / Plugin Add, or just Before Compile: 
> Use the metadata file to generate the symlinks if OS = OSX or Linux
>
> 2. Provide a specific mechanism to deal with frameworks
> a. Pre-publish: Find custom frameworks. (Which you can 
> actually do using plugin.xml), tgz them
> b. After Platform Add / Plugin Add, or just Before Compile: 
> Expand framework tgz if found
>
> (a) could be done via npm but (b) really has to be done via a Cordova 
> hook or be inherent to the iOS platform.
>
> Maybe the thing to do is to develop these hooks and add them to the 
> default template for plugins and in addition to the docs.  #1 is 
> likely a bit more robust.
>
> -Chuck
>
> -Original Message-
> From: Josh Soref [mailto:jso...@blackberry.com]
> Sent: Wednesday, May 6, 2015 11:05 AM
> To: dev@cordova.apache.org
> Subject: RE: Cordova Plugins with Symlinks
>
> It should be possible for our build system to convert some metadata 
> into symlinks which are fed to whatever build thing actually requires 
> them, but allows us to not have genuine symlinks in the working directory.
>
> The BlackBerry 10 project copies all the files it wants to package 
> over into another directory, other platforms should be able to do similar.
>
> > -Original Message-
> > From: Shazron [mailto:shaz...@gmail.com]
> > Sent: Wednesday, May 06, 2015 1:23 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Cordova Plugins with Symlinks
> >
> > Ordinarily I agree with Jesse's sentiment about not using symlinks 
> > but that is just the reality for .frameworks.
> >
> > That being said, I don't think we should do anything extra for 
> > authors _but_ instead provide a middle ground that you mentioned 
> > "provide guidance to plugin authors to work around this problem" and 
> > even as a pre-publish (or analysis) step that checks whether this 
> > might be a problem, and warns them.
> >
> > On Wed, May 6, 2015 at 9:54 AM, Chuck Lantz 
> > wrote:
> > > Yeah, I agree symlinks should be avoided, but what Ally 
> > > highlighted
> below
> > is that it is required in this case. ("@Ian Absolutely required. Not
> just for
> > Facebook, but all .framework files.") Given that statement, it seems
> that in
> > this case we need to have some sort of solution to remediate the 
> > problem does it not?
> > >
> > > -Chuck
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Wednesday, May 6, 2015 9:16 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: Cordova Plugins with Symlinks
> > >
> > > I think in this case we should be not be using symlinks. All of 
> > > our
> output
> > project types support adding a reference to a file or folder, we 
> > should leverage this directly.
> > > Of course, this could possibly lead to forward vs back slash 
> > > issues,
> but
> > should be easier than running hook hacks.
> > > At least I think we should explore this way.
> > >
> > >
> > >> On May 6, 2015, at 7:53 AM, Chuck Lantz  wrote:
> > >>
> > >> Hey folks,
> > >>
> > >> So I’ve started to see some issues come up with certain Cordova
> > plugins when devs are mixing a Windows and OSX environment together 
> > when developing an app. Digging into it a bit, it looks like root 
> > cause
> is that
> > there are some situations where iOS plugin implementations with 
> > custom frameworks that require symlinks - as described in the thread below.
> > >>
> > >> In addition to the situation mentioned in the thread, there's a
> second one
> > worth calling out: installing a plugin with symlinks on Windows on 
> > the
> NTFS
> > file system results in the symlinks becoming files.
> > >>
> > >> The workaround de

RE: Cordova Plugins with Symlinks

[Chuck Lantz]

Never mind - One of the things that requires a symlink is a file, so junctions 
won't work.  They also don't seem to move the contents when transferred via 
Samba.

On untar, we'd basically need to duplicate the files to get it to work at that 
point I think.  I did try that and it seems to work - Anyone know if there are 
potential unintended side-effects of doing that?

-Chuck

-Original Message-
From: Chuck Lantz [mailto:cla...@microsoft.com] 
Sent: Thursday, May 7, 2015 8:05 AM
To: dev@cordova.apache.org
Subject: RE: Cordova Plugins with Symlinks

Possibly using junctions. 

Actual symlinks require administrator privileges and there's no "sudo" like 
command which is why they're not used frequently.  You can create "folder 
junctions" (via mklink) without admin privs which would technically meet the 
need here since these are folder symlinks. 

One issue with junctions, however, is junctions look like folders when zipped 
or committed to a Git repo, so basically you just duplicate all the files. 
However, as long as frameworks will work with the contents duplicated rather 
than symlink'd, it make be an acceptable workaround.  Need to validate.

-Chuck

-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, May 7, 2015 6:55 AM
To: dev
Subject: Re: Cordova Plugins with Symlinks

Could we fix our un-tarring logic to create symlinks on windows?

On Wed, May 6, 2015 at 2:39 PM, Chuck Lantz  wrote:

> Yeah that was one of the alternatives I was thinking about as a part 
> of that pre-publish step I mentioned. Really, you'd need to either:
>
> 1. Provide a general mechanism for all symlinks using a metadata file
> a. Prep-publish: Run through and find paths to symlinks (which 
> is easy to do with node), store in a json file with the plugin
> b. After Platform Add / Plugin Add, or just Before Compile: 
> Use the metadata file to generate the symlinks if OS = OSX or Linux
>
> 2. Provide a specific mechanism to deal with frameworks
> a. Pre-publish: Find custom frameworks. (Which you can 
> actually do using plugin.xml), tgz them
> b. After Platform Add / Plugin Add, or just Before Compile: 
> Expand framework tgz if found
>
> (a) could be done via npm but (b) really has to be done via a Cordova 
> hook or be inherent to the iOS platform.
>
> Maybe the thing to do is to develop these hooks and add them to the 
> default template for plugins and in addition to the docs.  #1 is 
> likely a bit more robust.
>
> -Chuck
>
> -Original Message-
> From: Josh Soref [mailto:jso...@blackberry.com]
> Sent: Wednesday, May 6, 2015 11:05 AM
> To: dev@cordova.apache.org
> Subject: RE: Cordova Plugins with Symlinks
>
> It should be possible for our build system to convert some metadata 
> into symlinks which are fed to whatever build thing actually requires 
> them, but allows us to not have genuine symlinks in the working directory.
>
> The BlackBerry 10 project copies all the files it wants to package 
> over into another directory, other platforms should be able to do similar.
>
> > -Original Message-
> > From: Shazron [mailto:shaz...@gmail.com]
> > Sent: Wednesday, May 06, 2015 1:23 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Cordova Plugins with Symlinks
> >
> > Ordinarily I agree with Jesse's sentiment about not using symlinks 
> > but that is just the reality for .frameworks.
> >
> > That being said, I don't think we should do anything extra for 
> > authors _but_ instead provide a middle ground that you mentioned 
> > "provide guidance to plugin authors to work around this problem" and 
> > even as a pre-publish (or analysis) step that checks whether this 
> > might be a problem, and warns them.
> >
> > On Wed, May 6, 2015 at 9:54 AM, Chuck Lantz 
> > wrote:
> > > Yeah, I agree symlinks should be avoided, but what Ally 
> > > highlighted
> below
> > is that it is required in this case. ("@Ian Absolutely required. Not
> just for
> > Facebook, but all .framework files.") Given that statement, it seems
> that in
> > this case we need to have some sort of solution to remediate the 
> > problem does it not?
> > >
> > > -Chuck
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Wednesday, May 6, 2015 9:16 AM
> > > To: dev@cordova.apache.org
> > > Subject: Re: Cordova Plugins with Symlinks
> > >
> > > I think in this case we should be not be using symlinks. All of 
> > > our
> output
> > project types support adding a reference to a file or folder, we 
> > should leverage this directly.
> > > Of course, this could possibly lead to forward vs back slash 
> > > issues,
> but
> > should be easier than running hook hacks.
> > > At least I think we should explore this way.
> > >
> > >
> > >> On May 6, 2015, at 7:53 AM, Chuck Lantz  wrote:
> > >>
> > >> Hey folks,
> > >>
> > >> So I’ve started to see some issues come up with certain Cordova
> > plugins 

Cordova 5.0 user feedback - move to npm & whitelist plugin

[Nikhil Khandelwal]

There is a bunch of confusion with Cordova 5.0 users because of these two 
changes:

1. Move to npm for plugins (There have been multiple PRs trying to update 
plugin docs to reference the old id instead of the new one - because people are 
still using the old version of the CLI)

2. No network access in Android 4.0 without whitelist plugin:

  - https://issues.apache.org/jira/browse/CB-8969

  - 
http://stackoverflow.com/questions/29735597/cordova-5-0-0-android-app-can-not-connect-to-internet-using-android-4-0-0

- 
http://stackoverflow.com/questions/30060534/ajax-requests-fail-after-upgrading-to-cordova-5-0-cordova-android4-0



I think for the (1), I suggest we do the following:

1.   Update the plugin documentation that the old id can be used for older 
CLI versions.

2.   Either update the CPM with 1.0 versions of the plugins or have the CLI 
get core plugins from npm first then CPR even with the old id. Using the old id 
because they were hardcoded in IDEs etc, devs are getting older version of the 
plugins.



For (2), I think we should re-visit making whitelist part of the Android 
platform again or some other way of enabling network access by default. No 
network access (XHR) for a platform by default is a big change that's not well 
understood and not necessarily more secure. I'm new to this, but I did not 
fully understood the goals of moving the whitelisting to a plugin instead of it 
being part of the core.


Thanks,
Nikhil

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[brodybits]

Github user brodybits commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99931329
  
The Newtonsoft JSON library does seem much easier to use and perhaps more 
efficient as well, but unlike the .NET JSON `DataContractJsonSerializer`, 
Newtonsoft does not support serialization of arbitrary types. This becomes a 
problem with the cordova-file-plugin when it attempts to send a PluginResult 
with a byte array (`byte[]`) in response to a `readAsArrayBuffer` request. This 
is the cause of CB-8968, and it could affect other plugins as well.

I have identified two alternative solutions to fix CB-8968:

I. Fix `File.cs` in cordova-plugin-file to send the `PluginResult` with a 
normal integer array:

```diff
--- a/src/wp/File.cs
+++ b/src/wp/File.cs
@@ -695,7 +695,10 @@ public void readAsArrayBuffer(string options)
 buffer = readFileBytes(filePath, startPos, endPos, 
isoFile);
 }
 
-DispatchCommandResult(new 
PluginResult(PluginResult.Status.OK, buffer), callbackId);
+int[] bufferAsIntArray = new int[buffer.Length];
+for (int i=0; ihttp://stackoverflow.com/questions/15226921/how-to-serialize-byte-as-simple-json-array-and-not-as-base64-in-json-net

II. In `template/cordovalib/JSON/JsonHelper.cs` add a new function such as 
`public static string SerializeAny(object obj)` with what used to be the 
contents of `JSON.JsonHelper.Serialize`, and call this function instead of 
`JsonConvert.SerializeObject` in `PluginResult.cs`.

I am not sure which solution would have better performance. Solution II 
only goes through the data once, but solution II delegates the looping to the 
framework libraries, which *could* do the hard work in C/C++/assembly.

I am happy to issue a PR for either solution. Solution I would be easiest.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[purplecabbage]

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99934209
  
I think we should go with solution 1.
```
int[] bytesAsIntArray = Array.ConvertAll(buffer, c => (int)c);
```


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Cordova 5.0 user feedback - move to npm & whitelist plugin

[Raymond Camden]

> 2.   Either update the CPM with 1.0 versions of the plugins or have the 
> CLI get core plugins from npm first then CPR even with the old id. Using the 
> old id because they were hardcoded in IDEs etc, devs are getting older 
> version of the plugins.

>
> For (2), I think we should re-visit making whitelist part of the Android 
> platform again or some other way of enabling network access by default. No 
> network access (XHR) for a platform by default is a big change that's not 
> well understood and not necessarily more secure. I'm new to this, but I did 
> not fully understood the goals of moving the whitelisting to a plugin instead 
> of it being part of the core.


I'm reminded of the bump for 3.0 when everything became a plugin. All
of a sudden, none of the built in stuff (well, previously built in
stuff) worked anymore. I think folks got over that (and
bloggers/presenters/etc repeated it again and again), but this I can
see being a thorn in people's sides for a while. I don't necessarily
have a great answer (I'd like to see more discussion) but I think it
needs reconsidering.


-- 
===
Raymond Camden, Developer Advocate for MobileFirst at IBM

Email : raymondcam...@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

npm install cordova fails due to JSONStream dependency

[Nikhil Khandelwal]

This is breaking npm install of all recent versions of cordova:

λ npm install cordova
npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current: 
{"node":"0.12.0","npm":"2.5.1"})
npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current: 
{"node":"0.12.0","npm":"2.5.1"})
npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"} (current: 
{"node":"0.12.0","npm":"2.5.1"})
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe" "C:\\Program Files 
(x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "cordova"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ETARGET

npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3 <2.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget 
["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0","0.10.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! Please include the following file with any support request:
npm ERR! d:\apps\test\npm-debug.log

Our browserify dependency is at the heart of the problem: 
https://github.com/substack/node-browserify/issues/1249 but I don't understand 
enough of npm dependency management to figure out how this can be resolved. I'm 
still digging into this.

Thanks,
Nikhil

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[brodybits]

Github user brodybits commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99942506
  
Array.ConvertAll did not compile on Visual Studio Express 2013, and is 
apparently not supported for Metro or Silverlight. Figured out how to do this 
using Linq:

```diff
diff --git a/src/wp/File.cs b/src/wp/File.cs
index 941c9c8..085ef77 100644
--- a/src/wp/File.cs
+++ b/src/wp/File.cs
@@ -13,6 +13,7 @@
 */
 
 using System;
+using System.Linq;
 using System.Collections.Generic;
 using System.Diagnostics;
 using System.IO;
@@ -695,7 +696,9 @@ public void readAsArrayBuffer(string options)
 buffer = readFileBytes(filePath, startPos, endPos, 
isoFile);
 }
 
-DispatchCommandResult(new 
PluginResult(PluginResult.Status.OK, buffer), callbackId);
+int[] bufferAsIntArray = (from b in buffer select 
(int)b).ToArray();
+
+DispatchCommandResult(new 
PluginResult(PluginResult.Status.OK, bufferAsIntArray), callbackId);
 }
 catch (Exception ex)
 {
```

Please let me know if you want me to issue a PR.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: npm install cordova fails due to JSONStream dependency

[Jesse]

Yeah, it is browserify's dependency on JSONStream and a recent change to
npm that does not like package names with capital letters.

browserify has fixed it by changing their use from JSONStream to
jsonstream, however we are on a much older version of browserify, and can't
simply update to the most recent.

Probably we just need to give npm an hour or two to work it out.


@purplecabbage
risingj.com

On Thu, May 7, 2015 at 9:59 AM, Nikhil Khandelwal 
wrote:

> This is breaking npm install of all recent versions of cordova:
>
> λ npm install cordova
> npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.0","npm":"2.5.1"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.0","npm":"2.5.1"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.0","npm":"2.5.1"})
> npm ERR! Windows_NT 6.3.9600
> npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe" "C:\\Program
> Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "cordova"
> npm ERR! node v0.12.0
> npm ERR! npm  v2.5.1
> npm ERR! code ETARGET
>
> npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3 <2.0.0'
> npm ERR! notarget Valid install targets:
> npm ERR! notarget
> ["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0","0.10.0"]
> npm ERR! notarget
> npm ERR! notarget This is most likely not a problem with npm itself.
> npm ERR! notarget In most cases you or one of your dependencies are
> requesting
> npm ERR! notarget a package version that doesn't exist.
>
> npm ERR! Please include the following file with any support request:
> npm ERR! d:\apps\test\npm-debug.log
>
> Our browserify dependency is at the heart of the problem:
> https://github.com/substack/node-browserify/issues/1249 but I don't
> understand enough of npm dependency management to figure out how this can
> be resolved. I'm still digging into this.
>
> Thanks,
> Nikhil
>
>
>

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[purplecabbage]

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99943449
  
Looks good, send away.

@purplecabbage
risingj.com

On Thu, May 7, 2015 at 10:17 AM, Chris Brody 
wrote:

> Array.ConvertAll did not compile on Visual Studio Express 2013, and is
> apparently not supported for Metro or Silverlight. Figured out how to do
> this using Linq:
>
> diff --git a/src/wp/File.cs b/src/wp/File.cs
> index 941c9c8..085ef77 100644--- a/src/wp/File.cs+++ b/src/wp/File.cs@@ 
-13,6 +13,7 @@
>  */
>
>  using System;+using System.Linq;
>  using System.Collections.Generic;
>  using System.Diagnostics;
>  using System.IO;@@ -695,7 +696,9 @@ public void readAsArrayBuffer(string 
options)
>  buffer = readFileBytes(filePath, startPos, endPos, 
isoFile);
>  }
> -DispatchCommandResult(new 
PluginResult(PluginResult.Status.OK, buffer), callbackId);+
int[] bufferAsIntArray = (from b in buffer select (int)b).ToArray();++  
  DispatchCommandResult(new PluginResult(PluginResult.Status.OK, 
bufferAsIntArray), callbackId);
>  }
>  catch (Exception ex)
>  {
>
> Please let me know if you want me to issue a PR.
>
> —
> Reply to this email directly or view it on GitHub
> .
>



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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-file pull request: CB-8968 fix readAsArrayBuffer by...

[brodybits]

GitHub user brodybits opened a pull request:

https://github.com/apache/cordova-plugin-file/pull/115

CB-8968 fix readAsArrayBuffer by converting byte array to integer array 
using LINQ

Needed to fix CB-8968 since Newtonsoft JSON does not support JSON 
serialization of arbitrary types (ref: apache/cordova-wp8#79)

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

$ git pull https://github.com/brodybits/cordova-plugin-file CB-8968

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

https://github.com/apache/cordova-plugin-file/pull/115.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 #115


commit 7fb088b1eb7643ef0d03970e02d814e3899f16ac
Author: Chris Brody 
Date:   2015-05-07T17:30:03Z

CB-8968 fix readAsArrayBuffer by converting byte array to integer array 
using LINQ




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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: npm install cordova fails due to JSONStream dependency

[Steven Gill]

Nikhil, what version of npm are you using?
On May 7, 2015 10:21 AM, "Jesse"  wrote:

> Yeah, it is browserify's dependency on JSONStream and a recent change to
> npm that does not like package names with capital letters.
>
> browserify has fixed it by changing their use from JSONStream to
> jsonstream, however we are on a much older version of browserify, and can't
> simply update to the most recent.
>
> Probably we just need to give npm an hour or two to work it out.
>
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 9:59 AM, Nikhil Khandelwal 
> wrote:
>
> > This is breaking npm install of all recent versions of cordova:
> >
> > λ npm install cordova
> > npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current:
> > {"node":"0.12.0","npm":"2.5.1"})
> > npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> > {"node":"0.12.0","npm":"2.5.1"})
> > npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> > (current: {"node":"0.12.0","npm":"2.5.1"})
> > npm ERR! Windows_NT 6.3.9600
> > npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe" "C:\\Program
> > Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
> "cordova"
> > npm ERR! node v0.12.0
> > npm ERR! npm  v2.5.1
> > npm ERR! code ETARGET
> >
> > npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3
> <2.0.0'
> > npm ERR! notarget Valid install targets:
> > npm ERR! notarget
> >
> ["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0","0.10.0"]
> > npm ERR! notarget
> > npm ERR! notarget This is most likely not a problem with npm itself.
> > npm ERR! notarget In most cases you or one of your dependencies are
> > requesting
> > npm ERR! notarget a package version that doesn't exist.
> >
> > npm ERR! Please include the following file with any support request:
> > npm ERR! d:\apps\test\npm-debug.log
> >
> > Our browserify dependency is at the heart of the problem:
> > https://github.com/substack/node-browserify/issues/1249 but I don't
> > understand enough of npm dependency management to figure out how this can
> > be resolved. I'm still digging into this.
> >
> > Thanks,
> > Nikhil
> >
> >
> >
>

[GitHub] cordova-plugin-file pull request: CB-8968 fix readAsArrayBuffer by...

[brodybits]

Github user brodybits commented on the pull request:

https://github.com/apache/cordova-plugin-file/pull/115#issuecomment-99957767
  
NOTE: my ICLA was already submitted and accepted for cordova-wp8.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[brodybits]

Github user brodybits commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99960110
  
Issued PR to fix CB-8968 (automatic build failed, don't think it is my 
fault)


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-wp8 pull request: Added Newtonsoft json dll

[purplecabbage]

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-wp8/pull/79#issuecomment-99962513
  
nope, all auto build systems are hooped right now because of an issue with
Capitalized npm package names.

@purplecabbage
risingj.com

On Thu, May 7, 2015 at 10:54 AM, Chris Brody 
wrote:

> Issued PR to fix CB-8968 (automatic build failed, don't think it is my
> fault)
>
> —
> Reply to this email directly or view it on GitHub
> .
>



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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Also moving to a new team

[Marcel Kinard]

Staci Cooper and I are also moving to new positions. There already are 
backfills here coming up to speed: Karen Tran and James Dubee. You'll be seeing 
more of them here as time moves forward, joining Edna Morales.

This has been an absolutely awesome group to work with. You're smart, talented, 
passionate, and you deliver. I can't say that I had a single bad experience 
here. I will definitely miss it, I hope our paths cross again. Best wishes!

I may be tempted to dabble here in my off-hours. ;-)

-- Marcel Kinard

> On May 5, 2015, at 11:15 AM, Andrew Grieve  wrote:
> 
> As with Michal, you'll be seeing less of me around. My new full-time
> project will be on the Android port of Chrome.
> 
> Just want to make it clear that us moving to new teams has nothing to do
> with a lack of faith in the project, but rather is due to needing a change
> of scenery and exciting new projects becoming available here.
> 
> I'm super excited to see a new wave of committers joining the project! The
> momentum has certainly picked up:
> - Cordova-android 4.0.0 was huge
> - Plugins to npm was huge
> - Win10 and wkwebview will be massive launches as well!
> 
> Great time for Cordova! (or a bad one... you know... if you're measuring
> against the goal of becoming obsolete :P)


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: npm install cordova fails due to JSONStream dependency

[Murat Sutunc]

This is a major issue in NPM !!
 
There is a thread going on at github: https://github.com/npm/npm/issues/7195
"browserify versions 5.0.0 - 10.1.1 (10.1.2 is the latest) can't be installed 
because of JSONStream vs jsonstream on OS X and windows"

The real issue is browserify has a dependency on module-deps and JSONStream:
- browserify 7.1.0 has dependency on JSONStream 0.8.4
- browserify 7.1.0 has dependency on module-deps ^3.6.3
- module-deps 3.7.11 has dependency on jsonstream ^1.0.3

JSONStream and jsonstream are two separate repos. Lowercase jsonstream starts 
at version 1.0.0 and mixed case doesn't have any 1.0.0 version. npm install 
gets confused fails to install because it can't find both versions of the 
package in the same repo.

All the Cordova versions which depend on this version of browserify is 
currently broken!

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, May 7, 2015 10:45 AM
To: dev@cordova.apache.org
Subject: Re: npm install cordova fails due to JSONStream dependency

Nikhil, what version of npm are you using?
On May 7, 2015 10:21 AM, "Jesse"  wrote:

> Yeah, it is browserify's dependency on JSONStream and a recent change 
> to npm that does not like package names with capital letters.
>
> browserify has fixed it by changing their use from JSONStream to 
> jsonstream, however we are on a much older version of browserify, and 
> can't simply update to the most recent.
>
> Probably we just need to give npm an hour or two to work it out.
>
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 9:59 AM, Nikhil Khandelwal 
> 
> wrote:
>
> > This is breaking npm install of all recent versions of cordova:
> >
> > λ npm install cordova
> > npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current:
> > {"node":"0.12.0","npm":"2.5.1"})
> > npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> > {"node":"0.12.0","npm":"2.5.1"})
> > npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> > (current: {"node":"0.12.0","npm":"2.5.1"}) npm ERR! Windows_NT 
> > 6.3.9600 npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe" 
> > "C:\\Program Files 
> > (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
> "cordova"
> > npm ERR! node v0.12.0
> > npm ERR! npm  v2.5.1
> > npm ERR! code ETARGET
> >
> > npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3
> <2.0.0'
> > npm ERR! notarget Valid install targets:
> > npm ERR! notarget
> >
> ["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.
> 3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.
> 4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","
> 0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0"
> ,"0.10.0"]
> > npm ERR! notarget
> > npm ERR! notarget This is most likely not a problem with npm itself.
> > npm ERR! notarget In most cases you or one of your dependencies are 
> > requesting npm ERR! notarget a package version that doesn't exist.
> >
> > npm ERR! Please include the following file with any support request:
> > npm ERR! d:\apps\test\npm-debug.log
> >
> > Our browserify dependency is at the heart of the problem:
> > https://github.com/substack/node-browserify/issues/1249 but I don't 
> > understand enough of npm dependency management to figure out how 
> > this can be resolved. I'm still digging into this.
> >
> > Thanks,
> > Nikhil
> >
> >
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: npm install cordova fails due to JSONStream dependency

[Steven Gill]

How is this just popping up now! Crazy. I am going to update our browserify
dependency but this doesn't solve the issue of our current releases all
being broken.

On Thu, May 7, 2015 at 11:11 AM, Murat Sutunc  wrote:

> This is a major issue in NPM !!
>
> There is a thread going on at github:
> https://github.com/npm/npm/issues/7195
> "browserify versions 5.0.0 - 10.1.1 (10.1.2 is the latest) can't be
> installed because of JSONStream vs jsonstream on OS X and windows"
>
> The real issue is browserify has a dependency on module-deps and
> JSONStream:
> - browserify 7.1.0 has dependency on JSONStream 0.8.4
> - browserify 7.1.0 has dependency on module-deps ^3.6.3
> - module-deps 3.7.11 has dependency on jsonstream ^1.0.3
>
> JSONStream and jsonstream are two separate repos. Lowercase jsonstream
> starts at version 1.0.0 and mixed case doesn't have any 1.0.0 version. npm
> install gets confused fails to install because it can't find both versions
> of the package in the same repo.
>
> All the Cordova versions which depend on this version of browserify is
> currently broken!
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Thursday, May 7, 2015 10:45 AM
> To: dev@cordova.apache.org
> Subject: Re: npm install cordova fails due to JSONStream dependency
>
> Nikhil, what version of npm are you using?
> On May 7, 2015 10:21 AM, "Jesse"  wrote:
>
> > Yeah, it is browserify's dependency on JSONStream and a recent change
> > to npm that does not like package names with capital letters.
> >
> > browserify has fixed it by changing their use from JSONStream to
> > jsonstream, however we are on a much older version of browserify, and
> > can't simply update to the most recent.
> >
> > Probably we just need to give npm an hour or two to work it out.
> >
> >
> > @purplecabbage
> > risingj.com
> >
> > On Thu, May 7, 2015 at 9:59 AM, Nikhil Khandelwal
> > 
> > wrote:
> >
> > > This is breaking npm install of all recent versions of cordova:
> > >
> > > λ npm install cordova
> > > npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current:
> > > {"node":"0.12.0","npm":"2.5.1"})
> > > npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"}
> (current:
> > > {"node":"0.12.0","npm":"2.5.1"})
> > > npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> > > (current: {"node":"0.12.0","npm":"2.5.1"}) npm ERR! Windows_NT
> > > 6.3.9600 npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe"
> > > "C:\\Program Files
> > > (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
> > "cordova"
> > > npm ERR! node v0.12.0
> > > npm ERR! npm  v2.5.1
> > > npm ERR! code ETARGET
> > >
> > > npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3
> > <2.0.0'
> > > npm ERR! notarget Valid install targets:
> > > npm ERR! notarget
> > >
> > ["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.
> > 3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.
> > 4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","
> > 0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0"
> > ,"0.10.0"]
> > > npm ERR! notarget
> > > npm ERR! notarget This is most likely not a problem with npm itself.
> > > npm ERR! notarget In most cases you or one of your dependencies are
> > > requesting npm ERR! notarget a package version that doesn't exist.
> > >
> > > npm ERR! Please include the following file with any support request:
> > > npm ERR! d:\apps\test\npm-debug.log
> > >
> > > Our browserify dependency is at the heart of the problem:
> > > https://github.com/substack/node-browserify/issues/1249 but I don't
> > > understand enough of npm dependency management to figure out how
> > > this can be resolved. I'm still digging into this.
> > >
> > > Thanks,
> > > Nikhil
> > >
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: Also moving to a new team

[Michael Brooks]

>
> Staci Cooper and I are also moving to new positions. There already are
> backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> seeing more of them here as time moves forward, joining Edna Morales.


Awe, no Marcel! You've had a huge impact on this project and brought a
level of process and organization that we lacked and needed. You'll be
missed, so please keep in touch. I hope your next project is equally
exciting!

Michael

On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard  wrote:

> Staci Cooper and I are also moving to new positions. There already are
> backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> seeing more of them here as time moves forward, joining Edna Morales.
>
> This has been an absolutely awesome group to work with. You're smart,
> talented, passionate, and you deliver. I can't say that I had a single bad
> experience here. I will definitely miss it, I hope our paths cross again.
> Best wishes!
>
> I may be tempted to dabble here in my off-hours. ;-)
>
> -- Marcel Kinard
>
> > On May 5, 2015, at 11:15 AM, Andrew Grieve  wrote:
> >
> > As with Michal, you'll be seeing less of me around. My new full-time
> > project will be on the Android port of Chrome.
> >
> > Just want to make it clear that us moving to new teams has nothing to do
> > with a lack of faith in the project, but rather is due to needing a
> change
> > of scenery and exciting new projects becoming available here.
> >
> > I'm super excited to see a new wave of committers joining the project!
> The
> > momentum has certainly picked up:
> > - Cordova-android 4.0.0 was huge
> > - Plugins to npm was huge
> > - Win10 and wkwebview will be massive launches as well!
> >
> > Great time for Cordova! (or a bad one... you know... if you're measuring
> > against the goal of becoming obsolete :P)
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: Also moving to a new team

[Jesse]

Sorry to see you moving on Marcel, and Staci.
Your presence will be missed, you have done a lot here.
Best of luck in your new roles.

btw, you each deserve your own threads!

Cheers,
  Jesse

@purplecabbage
risingj.com

On Thu, May 7, 2015 at 11:36 AM, Michael Brooks 
wrote:

> >
> > Staci Cooper and I are also moving to new positions. There already are
> > backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> > seeing more of them here as time moves forward, joining Edna Morales.
>
>
> Awe, no Marcel! You've had a huge impact on this project and brought a
> level of process and organization that we lacked and needed. You'll be
> missed, so please keep in touch. I hope your next project is equally
> exciting!
>
> Michael
>
> On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard  wrote:
>
> > Staci Cooper and I are also moving to new positions. There already are
> > backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> > seeing more of them here as time moves forward, joining Edna Morales.
> >
> > This has been an absolutely awesome group to work with. You're smart,
> > talented, passionate, and you deliver. I can't say that I had a single
> bad
> > experience here. I will definitely miss it, I hope our paths cross again.
> > Best wishes!
> >
> > I may be tempted to dabble here in my off-hours. ;-)
> >
> > -- Marcel Kinard
> >
> > > On May 5, 2015, at 11:15 AM, Andrew Grieve 
> wrote:
> > >
> > > As with Michal, you'll be seeing less of me around. My new full-time
> > > project will be on the Android port of Chrome.
> > >
> > > Just want to make it clear that us moving to new teams has nothing to
> do
> > > with a lack of faith in the project, but rather is due to needing a
> > change
> > > of scenery and exciting new projects becoming available here.
> > >
> > > I'm super excited to see a new wave of committers joining the project!
> > The
> > > momentum has certainly picked up:
> > > - Cordova-android 4.0.0 was huge
> > > - Plugins to npm was huge
> > > - Win10 and wkwebview will be massive launches as well!
> > >
> > > Great time for Cordova! (or a bad one... you know... if you're
> measuring
> > > against the goal of becoming obsolete :P)
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

Re: Also moving to a new team

[Shazron]

Best of luck in your new roles Marcel and Staci!
*sad face*

On Thu, May 7, 2015 at 11:51 AM, Jesse  wrote:
> Sorry to see you moving on Marcel, and Staci.
> Your presence will be missed, you have done a lot here.
> Best of luck in your new roles.
>
> btw, you each deserve your own threads!
>
> Cheers,
>   Jesse
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 11:36 AM, Michael Brooks 
> wrote:
>
>> >
>> > Staci Cooper and I are also moving to new positions. There already are
>> > backfills here coming up to speed: Karen Tran and James Dubee. You'll be
>> > seeing more of them here as time moves forward, joining Edna Morales.
>>
>>
>> Awe, no Marcel! You've had a huge impact on this project and brought a
>> level of process and organization that we lacked and needed. You'll be
>> missed, so please keep in touch. I hope your next project is equally
>> exciting!
>>
>> Michael
>>
>> On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard  wrote:
>>
>> > Staci Cooper and I are also moving to new positions. There already are
>> > backfills here coming up to speed: Karen Tran and James Dubee. You'll be
>> > seeing more of them here as time moves forward, joining Edna Morales.
>> >
>> > This has been an absolutely awesome group to work with. You're smart,
>> > talented, passionate, and you deliver. I can't say that I had a single
>> bad
>> > experience here. I will definitely miss it, I hope our paths cross again.
>> > Best wishes!
>> >
>> > I may be tempted to dabble here in my off-hours. ;-)
>> >
>> > -- Marcel Kinard
>> >
>> > > On May 5, 2015, at 11:15 AM, Andrew Grieve 
>> wrote:
>> > >
>> > > As with Michal, you'll be seeing less of me around. My new full-time
>> > > project will be on the Android port of Chrome.
>> > >
>> > > Just want to make it clear that us moving to new teams has nothing to
>> do
>> > > with a lack of faith in the project, but rather is due to needing a
>> > change
>> > > of scenery and exciting new projects becoming available here.
>> > >
>> > > I'm super excited to see a new wave of committers joining the project!
>> > The
>> > > momentum has certainly picked up:
>> > > - Cordova-android 4.0.0 was huge
>> > > - Plugins to npm was huge
>> > > - Win10 and wkwebview will be massive launches as well!
>> > >
>> > > Great time for Cordova! (or a bad one... you know... if you're
>> measuring
>> > > against the goal of becoming obsolete :P)
>> >
>> >
>> > -
>> > 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] Rapid release of tools

[Steven Gill]

I think we should do a quick release to get npm install cordova working
again asap.

I have updated the browserify dependency on cordova-js which fixes the
problem.

Need to release cordova-js@3.9.1, cordova-lib@5.0.1, cordova-cli@5.0.1 and
plugman@0.23.2 with the new dependency.

Re: Also moving to a new team

[Steven Gill]

We will miss you both! Good luck you two!

On Thu, May 7, 2015 at 12:01 PM, Shazron  wrote:

> Best of luck in your new roles Marcel and Staci!
> *sad face*
>
> On Thu, May 7, 2015 at 11:51 AM, Jesse  wrote:
> > Sorry to see you moving on Marcel, and Staci.
> > Your presence will be missed, you have done a lot here.
> > Best of luck in your new roles.
> >
> > btw, you each deserve your own threads!
> >
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
> > On Thu, May 7, 2015 at 11:36 AM, Michael Brooks <
> mich...@michaelbrooks.ca>
> > wrote:
> >
> >> >
> >> > Staci Cooper and I are also moving to new positions. There already are
> >> > backfills here coming up to speed: Karen Tran and James Dubee. You'll
> be
> >> > seeing more of them here as time moves forward, joining Edna Morales.
> >>
> >>
> >> Awe, no Marcel! You've had a huge impact on this project and brought a
> >> level of process and organization that we lacked and needed. You'll be
> >> missed, so please keep in touch. I hope your next project is equally
> >> exciting!
> >>
> >> Michael
> >>
> >> On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard 
> wrote:
> >>
> >> > Staci Cooper and I are also moving to new positions. There already are
> >> > backfills here coming up to speed: Karen Tran and James Dubee. You'll
> be
> >> > seeing more of them here as time moves forward, joining Edna Morales.
> >> >
> >> > This has been an absolutely awesome group to work with. You're smart,
> >> > talented, passionate, and you deliver. I can't say that I had a single
> >> bad
> >> > experience here. I will definitely miss it, I hope our paths cross
> again.
> >> > Best wishes!
> >> >
> >> > I may be tempted to dabble here in my off-hours. ;-)
> >> >
> >> > -- Marcel Kinard
> >> >
> >> > > On May 5, 2015, at 11:15 AM, Andrew Grieve 
> >> wrote:
> >> > >
> >> > > As with Michal, you'll be seeing less of me around. My new full-time
> >> > > project will be on the Android port of Chrome.
> >> > >
> >> > > Just want to make it clear that us moving to new teams has nothing
> to
> >> do
> >> > > with a lack of faith in the project, but rather is due to needing a
> >> > change
> >> > > of scenery and exciting new projects becoming available here.
> >> > >
> >> > > I'm super excited to see a new wave of committers joining the
> project!
> >> > The
> >> > > momentum has certainly picked up:
> >> > > - Cordova-android 4.0.0 was huge
> >> > > - Plugins to npm was huge
> >> > > - Win10 and wkwebview will be massive launches as well!
> >> > >
> >> > > Great time for Cordova! (or a bad one... you know... if you're
> >> measuring
> >> > > against the goal of becoming obsolete :P)
> >> >
> >> >
> >> > -
> >> > 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] Rapid release of tools

[Jesse]

Given that all downstream distributions are broken currently, can we do an
accelerated vote?
Are we introducing any other code that would slow us down? or can we simply
update+republish package.json files?

@purplecabbage
risingj.com

On Thu, May 7, 2015 at 12:01 PM, Steven Gill  wrote:

> I think we should do a quick release to get npm install cordova working
> again asap.
>
> I have updated the browserify dependency on cordova-js which fixes the
> problem.
>
> Need to release cordova-js@3.9.1, cordova-lib@5.0.1, cordova-cli@5.0.1 and
> plugman@0.23.2 with the new dependency.
>

Re: [DISCUSS] Rapid release of tools

[Steven Gill]

I am thinking we release off our previous release branches with this one
change. This needs to get out asap. I'm all for an accelerated vote.



On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:

> Given that all downstream distributions are broken currently, can we do an
> accelerated vote?
> Are we introducing any other code that would slow us down? or can we simply
> update+republish package.json files?
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
> wrote:
>
> > I think we should do a quick release to get npm install cordova working
> > again asap.
> >
> > I have updated the browserify dependency on cordova-js which fixes the
> > problem.
> >
> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1, cordova-cli@5.0.1
> and
> > plugman@0.23.2 with the new dependency.
> >
>

RE: [DISCUSS] Rapid release of tools

[Chuck Lantz]

Definitely.

Note that 4.3.0 is also broken - We likely need to look at a 4.3.1 given the 
level of change in 5.0.0. 

-Chuck

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, May 7, 2015 12:08 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Rapid release of tools

I am thinking we release off our previous release branches with this one 
change. This needs to get out asap. I'm all for an accelerated vote.



On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:

> Given that all downstream distributions are broken currently, can we 
> do an accelerated vote?
> Are we introducing any other code that would slow us down? or can we 
> simply
> update+republish package.json files?
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
> wrote:
>
> > I think we should do a quick release to get npm install cordova 
> > working again asap.
> >
> > I have updated the browserify dependency on cordova-js which fixes 
> > the problem.
> >
> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1, 
> > cordova-cli@5.0.1
> and
> > plugman@0.23.2 with the new dependency.
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-3360 Set custom User-Agent

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/284#issuecomment-99987621
  
note: this is slated for cordova-ios 4.0.x release


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [DISCUSS] Rapid release of tools

[Parashuram N (MS OPEN TECH)]

I think we should do an accelerated vote - 72 hour window is only a suggestion, 
and if the community believes, we should start a DISCUSS and a VOTE thread 
soon. 

-Original Message-
From: Chuck Lantz [mailto:cla...@microsoft.com] 
Sent: Thursday, May 7, 2015 12:13 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Rapid release of tools

Definitely.

Note that 4.3.0 is also broken - We likely need to look at a 4.3.1 given the 
level of change in 5.0.0. 

-Chuck

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Thursday, May 7, 2015 12:08 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Rapid release of tools

I am thinking we release off our previous release branches with this one 
change. This needs to get out asap. I'm all for an accelerated vote.



On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:

> Given that all downstream distributions are broken currently, can we 
> do an accelerated vote?
> Are we introducing any other code that would slow us down? or can we 
> simply
> update+republish package.json files?
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
> wrote:
>
> > I think we should do a quick release to get npm install cordova 
> > working again asap.
> >
> > I have updated the browserify dependency on cordova-js which fixes 
> > the problem.
> >
> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
> > cordova-cli@5.0.1
> and
> > plugman@0.23.2 with the new dependency.
> >
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Rapid release of tools

[Shazron]

+1 release off previous, with this one change only.

On Thu, May 7, 2015 at 12:07 PM, Steven Gill  wrote:
> I am thinking we release off our previous release branches with this one
> change. This needs to get out asap. I'm all for an accelerated vote.
>
>
>
> On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:
>
>> Given that all downstream distributions are broken currently, can we do an
>> accelerated vote?
>> Are we introducing any other code that would slow us down? or can we simply
>> update+republish package.json files?
>>
>> @purplecabbage
>> risingj.com
>>
>> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
>> wrote:
>>
>> > I think we should do a quick release to get npm install cordova working
>> > again asap.
>> >
>> > I have updated the browserify dependency on cordova-js which fixes the
>> > problem.
>> >
>> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1, cordova-cli@5.0.1
>> and
>> > plugman@0.23.2 with the new dependency.
>> >
>>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: npm install cordova fails due to JSONStream dependency

[Shazron]

someone already filed: https://issues.apache.org/jira/browse/CB-8985

On Thu, May 7, 2015 at 11:26 AM, Steven Gill  wrote:
> How is this just popping up now! Crazy. I am going to update our browserify
> dependency but this doesn't solve the issue of our current releases all
> being broken.
>
> On Thu, May 7, 2015 at 11:11 AM, Murat Sutunc  wrote:
>
>> This is a major issue in NPM !!
>>
>> There is a thread going on at github:
>> https://github.com/npm/npm/issues/7195
>> "browserify versions 5.0.0 - 10.1.1 (10.1.2 is the latest) can't be
>> installed because of JSONStream vs jsonstream on OS X and windows"
>>
>> The real issue is browserify has a dependency on module-deps and
>> JSONStream:
>> - browserify 7.1.0 has dependency on JSONStream 0.8.4
>> - browserify 7.1.0 has dependency on module-deps ^3.6.3
>> - module-deps 3.7.11 has dependency on jsonstream ^1.0.3
>>
>> JSONStream and jsonstream are two separate repos. Lowercase jsonstream
>> starts at version 1.0.0 and mixed case doesn't have any 1.0.0 version. npm
>> install gets confused fails to install because it can't find both versions
>> of the package in the same repo.
>>
>> All the Cordova versions which depend on this version of browserify is
>> currently broken!
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Thursday, May 7, 2015 10:45 AM
>> To: dev@cordova.apache.org
>> Subject: Re: npm install cordova fails due to JSONStream dependency
>>
>> Nikhil, what version of npm are you using?
>> On May 7, 2015 10:21 AM, "Jesse"  wrote:
>>
>> > Yeah, it is browserify's dependency on JSONStream and a recent change
>> > to npm that does not like package names with capital letters.
>> >
>> > browserify has fixed it by changing their use from JSONStream to
>> > jsonstream, however we are on a much older version of browserify, and
>> > can't simply update to the most recent.
>> >
>> > Probably we just need to give npm an hour or two to work it out.
>> >
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> > On Thu, May 7, 2015 at 9:59 AM, Nikhil Khandelwal
>> > 
>> > wrote:
>> >
>> > > This is breaking npm install of all recent versions of cordova:
>> > >
>> > > λ npm install cordova
>> > > npm WARN engine cordova-js@3.9.0: wanted: {"node":"~0.10.x"} (current:
>> > > {"node":"0.12.0","npm":"2.5.1"})
>> > > npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"}
>> (current:
>> > > {"node":"0.12.0","npm":"2.5.1"})
>> > > npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
>> > > (current: {"node":"0.12.0","npm":"2.5.1"}) npm ERR! Windows_NT
>> > > 6.3.9600 npm ERR! argv "C:\\Program Files (x86)\\nodejsnode.exe"
>> > > "C:\\Program Files
>> > > (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
>> > "cordova"
>> > > npm ERR! node v0.12.0
>> > > npm ERR! npm  v2.5.1
>> > > npm ERR! code ETARGET
>> > >
>> > > npm ERR! notarget No compatible version found: JSONStream@'>=1.0.3
>> > <2.0.0'
>> > > npm ERR! notarget Valid install targets:
>> > > npm ERR! notarget
>> > >
>> > ["0.0.0","0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.2.2","0.2.
>> > 3","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2","0.4.3","0.
>> > 4.4","0.5.0","0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","
>> > 0.8.0","0.7.2","0.7.3","0.7.4","0.8.1","0.8.2","0.8.3","0.8.4","0.9.0"
>> > ,"0.10.0"]
>> > > npm ERR! notarget
>> > > npm ERR! notarget This is most likely not a problem with npm itself.
>> > > npm ERR! notarget In most cases you or one of your dependencies are
>> > > requesting npm ERR! notarget a package version that doesn't exist.
>> > >
>> > > npm ERR! Please include the following file with any support request:
>> > > npm ERR! d:\apps\test\npm-debug.log
>> > >
>> > > Our browserify dependency is at the heart of the problem:
>> > > https://github.com/substack/node-browserify/issues/1249 but I don't
>> > > understand enough of npm dependency management to figure out how
>> > > this can be resolved. I'm still digging into this.
>> > >
>> > > Thanks,
>> > > Nikhil
>> > >
>> > >
>> > >
>> >
>>
>> -
>> 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] Rapid release of tools

[Steven Gill]

i'm working on getting the release ready

On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:

> +1 release off previous, with this one change only.
>
> On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
> wrote:
> > I am thinking we release off our previous release branches with this one
> > change. This needs to get out asap. I'm all for an accelerated vote.
> >
> >
> >
> > On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:
> >
> >> Given that all downstream distributions are broken currently, can we do
> an
> >> accelerated vote?
> >> Are we introducing any other code that would slow us down? or can we
> simply
> >> update+republish package.json files?
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
> >> wrote:
> >>
> >> > I think we should do a quick release to get npm install cordova
> working
> >> > again asap.
> >> >
> >> > I have updated the browserify dependency on cordova-js which fixes the
> >> > problem.
> >> >
> >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
> cordova-cli@5.0.1
> >> and
> >> > plugman@0.23.2 with the new dependency.
> >> >
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

RE: Help for Crosswalk Chromium webview consumption.

[Andrew M Trice]

Quick update here... Crosswalk is now officially supported as part of
Cordova 4.0:
https://cordova.apache.org/announcements/2015/04/15/cordova-android-4.0.0.html

This is made available via that cordova-plugin-crosswalk-webview plugin:
https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview

Thanks,
Andy

Andrew Trice
IBM MobileFirst Developer Advocate

email: amtr...@us.ibm.com
mobile: 571-334-9986
twitter: @andytrice
blog: http://tricedesigns.com




From:   "Vishnu Prakash" 
To: "'Bnaya Peretz'" 
Cc: "'Alexander Biemann'" ,
, 
Date:   04/30/2015 10:49 AM
Subject:RE: Help for Crosswalk Chromium webview consumption.



Dear Bnaya,Alexander

Greetings



I am building a web view for my native app. As suggested by you, I will
like to stick with the xwalk and not to the Cordova.



Today I am able to create a sample application where using
xwalk-core-lib ,I am able to launch a sample website. That was the
objective. Now onwards, I will be using my proof of concept in my project.



Really appreciate all your support. Looking forward to work together with
you.



Warm Regards,

Vishnu



From: Bnaya Peretz [mailto:m...@bnaya.net]
Sent: Wednesday, April 29, 2015 6:40 PM
To: Vishnu Prakash
Cc: Alexander Biemann; crosswalk-h...@ml01.01.org; dev@cordova.apache.org
Subject: Re: Help for Crosswalk Chromium webview consumption.



Are you building web based app or the webview is just a part from a native
app?

If your app is web based one i would suggest to stick with cordova project.

if you want to import crosswalk to your own eclipse project i have never
done it myself but you can follow
http://stackoverflow.com/a/23949505/711152



On Wed, Apr 29, 2015 at 4:03 PM, Vishnu Prakash mailto:vishnu.prak...@42gears.com> > wrote:

Hi Bnaya, Alexander



I hope everything is awesome at your end and really appreciate your quick
help. I explored today about  Cordova plugin and was able to build a sample
HelloWorld program and launch on my device.

This is great and has given me confidence. I was exploring how I can use
the same plugin to my existing apps in Eclipse.



Can you please guide me how to use the Cordova WebView plugin to an already
existing solution to simply consume the WebView plugin.



Really appreciate your help.

Warm Regards,

Vishnu







From: Bnaya Peretz [mailto:m...@bnaya.net  ]
Sent: Tuesday, April 28, 2015 6:01 PM
To: Vishnu Prakash
Cc: Alexander Biemann; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org> ; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org>
Subject: Re: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.



You can create cordova android project and install the
https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview
plugin
Read more here:
https://cordova.apache.org/announcements/2015/04/15/cordova-android-4.0.0.html




On Tue, Apr 28, 2015 at 1:06 PM, Vishnu Prakash mailto:vishnu.prak...@42gears.com> > wrote:

Dear Alexander,

I really appreciate your time and help.



I have got the .aar file from the url and extracted it. I also see the .jar
file. I also used the Java decompile tool for the  .jar file and can see
the .class files/methods etc.



May I request you to help me with a sample application program how I can
consume the above .jar files  to load a url like
https://crosswalk-project.org  for Chromium WebView. Any documentation also
will be highly appreciated.



Warm Regards,

Vishnu



From: Alexander Biemann [mailto:abiem...@hotmail.com <
mailto:abiem...@hotmail.com> ]
Sent: Tuesday, April 28, 2015 11:51 AM
To: Vishnu Prakash; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org>
Subject: RE: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.



Vishnu,

just take the .aar from the URL that you mentioned and include it in your
project.
aar's are easy to work with, follow this guidance...
http://stackoverflow.com/a/29832424/550471

Regards,
Alexander


  _


From: vishnu.prak...@42gears.com 
To: crosswalk-h...@ml01.01.org 
Date: Tue, 28 Apr 2015 09:33:47 +0530
Subject: Re: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.

Resending post subscription. Looking forward for all your support.

Vishnu



From: Vishnu Prakash [mailto:vishnu.prak...@42gears.com]
Sent: Monday, April 27, 2015 6:18 PM
To: 'crosswalk-h...@lists.crosswalk-project.org <
mailto:crosswalk-h...@lists.crosswalk-project.org> '
Cc: 'pranay.choudh...@42gears.com  ';
'Rinkalkumar'; Kaushik Sindhu; 'vic...@costan.us 
'
Subject: Help for Crosswalk Chromium webview consumption.



Hi Crosswalk team,

Greetings!!!



I was looking forward to take help of the Cross walk project in my sample
application. My objective is to consume  the latest Chromium WebView to
browse one website to begin with.



Can you please co

RE: Help for Crosswalk Chromium webview consumption.

[Andrew M Trice]

Sorry all, wrong thread.  ignore me.. :)


Andrew Trice
IBM MobileFirst Developer Advocate

email: amtr...@us.ibm.com
mobile: 571-334-9986
twitter: @andytrice
blog: http://tricedesigns.com




From:   "Vishnu Prakash" 
To: "'Bnaya Peretz'" 
Cc: "'Alexander Biemann'" ,
, 
Date:   04/30/2015 10:49 AM
Subject:RE: Help for Crosswalk Chromium webview consumption.



Dear Bnaya,Alexander

Greetings



I am building a web view for my native app. As suggested by you, I will
like to stick with the xwalk and not to the Cordova.



Today I am able to create a sample application where using
xwalk-core-lib ,I am able to launch a sample website. That was the
objective. Now onwards, I will be using my proof of concept in my project.



Really appreciate all your support. Looking forward to work together with
you.



Warm Regards,

Vishnu



From: Bnaya Peretz [mailto:m...@bnaya.net]
Sent: Wednesday, April 29, 2015 6:40 PM
To: Vishnu Prakash
Cc: Alexander Biemann; crosswalk-h...@ml01.01.org; dev@cordova.apache.org
Subject: Re: Help for Crosswalk Chromium webview consumption.



Are you building web based app or the webview is just a part from a native
app?

If your app is web based one i would suggest to stick with cordova project.

if you want to import crosswalk to your own eclipse project i have never
done it myself but you can follow
http://stackoverflow.com/a/23949505/711152



On Wed, Apr 29, 2015 at 4:03 PM, Vishnu Prakash mailto:vishnu.prak...@42gears.com> > wrote:

Hi Bnaya, Alexander



I hope everything is awesome at your end and really appreciate your quick
help. I explored today about  Cordova plugin and was able to build a sample
HelloWorld program and launch on my device.

This is great and has given me confidence. I was exploring how I can use
the same plugin to my existing apps in Eclipse.



Can you please guide me how to use the Cordova WebView plugin to an already
existing solution to simply consume the WebView plugin.



Really appreciate your help.

Warm Regards,

Vishnu







From: Bnaya Peretz [mailto:m...@bnaya.net  ]
Sent: Tuesday, April 28, 2015 6:01 PM
To: Vishnu Prakash
Cc: Alexander Biemann; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org> ; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org>
Subject: Re: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.



You can create cordova android project and install the
https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview
plugin
Read more here:
https://cordova.apache.org/announcements/2015/04/15/cordova-android-4.0.0.html




On Tue, Apr 28, 2015 at 1:06 PM, Vishnu Prakash mailto:vishnu.prak...@42gears.com> > wrote:

Dear Alexander,

I really appreciate your time and help.



I have got the .aar file from the url and extracted it. I also see the .jar
file. I also used the Java decompile tool for the  .jar file and can see
the .class files/methods etc.



May I request you to help me with a sample application program how I can
consume the above .jar files  to load a url like
https://crosswalk-project.org  for Chromium WebView. Any documentation also
will be highly appreciated.



Warm Regards,

Vishnu



From: Alexander Biemann [mailto:abiem...@hotmail.com <
mailto:abiem...@hotmail.com> ]
Sent: Tuesday, April 28, 2015 11:51 AM
To: Vishnu Prakash; crosswalk-h...@ml01.01.org <
mailto:crosswalk-h...@ml01.01.org>
Subject: RE: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.



Vishnu,

just take the .aar from the URL that you mentioned and include it in your
project.
aar's are easy to work with, follow this guidance...
http://stackoverflow.com/a/29832424/550471

Regards,
Alexander


  _


From: vishnu.prak...@42gears.com 
To: crosswalk-h...@ml01.01.org 
Date: Tue, 28 Apr 2015 09:33:47 +0530
Subject: Re: [Crosswalk-help] Help for Crosswalk Chromium webview
consumption.

Resending post subscription. Looking forward for all your support.

Vishnu



From: Vishnu Prakash [mailto:vishnu.prak...@42gears.com]
Sent: Monday, April 27, 2015 6:18 PM
To: 'crosswalk-h...@lists.crosswalk-project.org <
mailto:crosswalk-h...@lists.crosswalk-project.org> '
Cc: 'pranay.choudh...@42gears.com  ';
'Rinkalkumar'; Kaushik Sindhu; 'vic...@costan.us 
'
Subject: Help for Crosswalk Chromium webview consumption.



Hi Crosswalk team,

Greetings!!!



I was looking forward to take help of the Cross walk project in my sample
application. My objective is to consume  the latest Chromium WebView to
browse one website to begin with.



Can you please connect me with the concerned team who can help me with the
following request.



1)  Is there any documentation of the following solution listed on
github https://github.com/crosswalk-project/chromium-crosswalk.

I can see the code but not aware how to use it. I browsed thro

Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Jesse]

+1
* coho verify-archive
* unpacked and verified each plugin could be installed, and run on ios
* manually verified version numbers throughout all package.json and
plugin.xml files

@purplecabbage
risingj.com

On Wed, May 6, 2015 at 5:42 PM, Steven Gill  wrote:

> Please review and vote on the release of this plugins release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> Release issue: https://issues.apache.org/jira/browse/CB-8959
>
> The plugins have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-camera: 1.1.0 (19feee9cb0)
> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
> cordova-plugin-dialogs: 1.1.0 (439372988b)
> cordova-plugin-vibration: 1.1.0 (4d316e2555)
>
> Upon a successful vote I will upload the archives to dist/, upload
> them to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and
> subdependencies have Apache-compatible licenses
>

RE: [DISCUSS] Rapid release of tools

[Murat Sutunc]

Wait guys. I think we should hold on for a sec.

There are 3 possible scenarios: 
1- We bump up our dependencies, latest version of Cordova is fixed but older 
ones remain broken.
2- Browserify and/or module-deps can roll back (unpublish perhaps). Which will 
fix the issue for all cordova until npm makes the fix.
3- NPM makes a quick fix. 

If we bump Cordova and browserify and module-deps decides to roll back, we'll 
be in trouble. I think the correct approach here is to talk with NPM and see 
what they suggest. If they commit on fixing this issue asap, browserify and 
module-deps can rollback and republish once everything is fixed. If you look at 
browserify and module-deps, using lowercase repos is a pretty recent change and 
there's probably less dependencies out there than Cordova.

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, May 7, 2015 12:47 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Rapid release of tools

i'm working on getting the release ready

On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:

> +1 release off previous, with this one change only.
>
> On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
> wrote:
> > I am thinking we release off our previous release branches with this 
> > one change. This needs to get out asap. I'm all for an accelerated vote.
> >
> >
> >
> > On Thu, May 7, 2015 at 12:05 PM, Jesse  wrote:
> >
> >> Given that all downstream distributions are broken currently, can 
> >> we do
> an
> >> accelerated vote?
> >> Are we introducing any other code that would slow us down? or can 
> >> we
> simply
> >> update+republish package.json files?
> >>
> >> @purplecabbage
> >> risingj.com
> >>
> >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
> >> 
> >> wrote:
> >>
> >> > I think we should do a quick release to get npm install cordova
> working
> >> > again asap.
> >> >
> >> > I have updated the browserify dependency on cordova-js which 
> >> > fixes the problem.
> >> >
> >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
> cordova-cli@5.0.1
> >> and
> >> > plugman@0.23.2 with the new dependency.
> >> >
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Rapid release of tools

[Steven Gill]

Looks like they just fixed the issue by using an older version of npm to
publish JSONStream 1.0.2 and 1.0.3. No need for a release! Woot!

FTR, I don't think the hotfix would have caused any issues for us as long
as they kept browserify 10.1.2 around.



On Thu, May 7, 2015 at 1:01 PM, Murat Sutunc  wrote:

> Wait guys. I think we should hold on for a sec.
>
> There are 3 possible scenarios:
> 1- We bump up our dependencies, latest version of Cordova is fixed but
> older ones remain broken.
> 2- Browserify and/or module-deps can roll back (unpublish perhaps). Which
> will fix the issue for all cordova until npm makes the fix.
> 3- NPM makes a quick fix.
>
> If we bump Cordova and browserify and module-deps decides to roll back,
> we'll be in trouble. I think the correct approach here is to talk with NPM
> and see what they suggest. If they commit on fixing this issue asap,
> browserify and module-deps can rollback and republish once everything is
> fixed. If you look at browserify and module-deps, using lowercase repos is
> a pretty recent change and there's probably less dependencies out there
> than Cordova.
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Thursday, May 7, 2015 12:47 PM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Rapid release of tools
>
> i'm working on getting the release ready
>
> On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:
>
> > +1 release off previous, with this one change only.
> >
> > On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
> > wrote:
> > > I am thinking we release off our previous release branches with this
> > > one change. This needs to get out asap. I'm all for an accelerated
> vote.
> > >
> > >
> > >
> > > On Thu, May 7, 2015 at 12:05 PM, Jesse 
> wrote:
> > >
> > >> Given that all downstream distributions are broken currently, can
> > >> we do
> > an
> > >> accelerated vote?
> > >> Are we introducing any other code that would slow us down? or can
> > >> we
> > simply
> > >> update+republish package.json files?
> > >>
> > >> @purplecabbage
> > >> risingj.com
> > >>
> > >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill
> > >> 
> > >> wrote:
> > >>
> > >> > I think we should do a quick release to get npm install cordova
> > working
> > >> > again asap.
> > >> >
> > >> > I have updated the browserify dependency on cordova-js which
> > >> > fixes the problem.
> > >> >
> > >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
> > cordova-cli@5.0.1
> > >> and
> > >> > plugman@0.23.2 with the new dependency.
> > >> >
> > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: [DISCUSS] Rapid release of tools

[Steven Gill]

I have already published cordova-js@3.9.1 and cordova-lib@5.0.1 under the
RC flag before I saw your message. I will unpublish them, delete tags,
revert commits, etc. :(



On Thu, May 7, 2015 at 1:16 PM, Steven Gill  wrote:

> Looks like they just fixed the issue by using an older version of npm to
> publish JSONStream 1.0.2 and 1.0.3. No need for a release! Woot!
>
> FTR, I don't think the hotfix would have caused any issues for us as long
> as they kept browserify 10.1.2 around.
>
>
>
> On Thu, May 7, 2015 at 1:01 PM, Murat Sutunc 
> wrote:
>
>> Wait guys. I think we should hold on for a sec.
>>
>> There are 3 possible scenarios:
>> 1- We bump up our dependencies, latest version of Cordova is fixed but
>> older ones remain broken.
>> 2- Browserify and/or module-deps can roll back (unpublish perhaps). Which
>> will fix the issue for all cordova until npm makes the fix.
>> 3- NPM makes a quick fix.
>>
>> If we bump Cordova and browserify and module-deps decides to roll back,
>> we'll be in trouble. I think the correct approach here is to talk with NPM
>> and see what they suggest. If they commit on fixing this issue asap,
>> browserify and module-deps can rollback and republish once everything is
>> fixed. If you look at browserify and module-deps, using lowercase repos is
>> a pretty recent change and there's probably less dependencies out there
>> than Cordova.
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Thursday, May 7, 2015 12:47 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Rapid release of tools
>>
>> i'm working on getting the release ready
>>
>> On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:
>>
>> > +1 release off previous, with this one change only.
>> >
>> > On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
>> > wrote:
>> > > I am thinking we release off our previous release branches with this
>> > > one change. This needs to get out asap. I'm all for an accelerated
>> vote.
>> > >
>> > >
>> > >
>> > > On Thu, May 7, 2015 at 12:05 PM, Jesse 
>> wrote:
>> > >
>> > >> Given that all downstream distributions are broken currently, can
>> > >> we do
>> > an
>> > >> accelerated vote?
>> > >> Are we introducing any other code that would slow us down? or can
>> > >> we
>> > simply
>> > >> update+republish package.json files?
>> > >>
>> > >> @purplecabbage
>> > >> risingj.com
>> > >>
>> > >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill
>> > >> 
>> > >> wrote:
>> > >>
>> > >> > I think we should do a quick release to get npm install cordova
>> > working
>> > >> > again asap.
>> > >> >
>> > >> > I have updated the browserify dependency on cordova-js which
>> > >> > fixes the problem.
>> > >> >
>> > >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
>> > cordova-cli@5.0.1
>> > >> and
>> > >> > plugman@0.23.2 with the new dependency.
>> > >> >
>> > >>
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > For additional commands, e-mail: dev-h...@cordova.apache.org
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>

RE: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Nikhil Khandelwal]

* Verified signatures and hashes
* Verified tags
* Verified plugins added correctly to blank app
* Verified blank app can be successfully ran and built
* Ran smoke testing of mobilespec app
* Performed manual ad-hoc testing
* Verified Release Notes

I vote +1.

Thanks,
Nikhil


-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, May 7, 2015 12:57 PM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, 
device-motion)

+1
* coho verify-archive
* unpacked and verified each plugin could be installed, and run on ios
* manually verified version numbers throughout all package.json and plugin.xml 
files

@purplecabbage
risingj.com

On Wed, May 6, 2015 at 5:42 PM, Steven Gill  wrote:

> Please review and vote on the release of this plugins release by 
> replying to this email (and keep discussion on the DISCUSS thread)
>
> Release issue: https://issues.apache.org/jira/browse/CB-8959
>
> The plugins have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-camera: 1.1.0 (19feee9cb0)
> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
> cordova-plugin-dialogs: 1.1.0 (439372988b)
> cordova-plugin-vibration: 1.1.0 (4d316e2555)
>
> Upon a successful vote I will upload the archives to dist/, upload 
> them to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
>

Re: Also moving to a new team

[Tommy-Carlos Williams]

:(

That is very sad. You will all be missed. 

Good luck with whatever you do next. 




> On 8 May 2015, at 04:04, Marcel Kinard  wrote:
> 
> Staci Cooper and I are also moving to new positions. There already are 
> backfills here coming up to speed: Karen Tran and James Dubee. You'll be 
> seeing more of them here as time moves forward, joining Edna Morales.
> 
> This has been an absolutely awesome group to work with. You're smart, 
> talented, passionate, and you deliver. I can't say that I had a single bad 
> experience here. I will definitely miss it, I hope our paths cross again. 
> Best wishes!
> 
> I may be tempted to dabble here in my off-hours. ;-)
> 
> -- Marcel Kinard
> 
>> On May 5, 2015, at 11:15 AM, Andrew Grieve  wrote:
>> 
>> As with Michal, you'll be seeing less of me around. My new full-time
>> project will be on the Android port of Chrome.
>> 
>> Just want to make it clear that us moving to new teams has nothing to do
>> with a lack of faith in the project, but rather is due to needing a change
>> of scenery and exciting new projects becoming available here.
>> 
>> I'm super excited to see a new wave of committers joining the project! The
>> momentum has certainly picked up:
>> - Cordova-android 4.0.0 was huge
>> - Plugins to npm was huge
>> - Win10 and wkwebview will be massive launches as well!
>> 
>> Great time for Cordova! (or a bad one... you know... if you're measuring
>> against the goal of becoming obsolete :P)
> 
> 
> -
> 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] Rapid release of tools

[Murat Sutunc]

Ahh, thanks Steven for all the work! Glad to see Cordova working again!

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com] 
Sent: Thursday, May 7, 2015 1:19 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Rapid release of tools

I have already published cordova-js@3.9.1 and cordova-lib@5.0.1 under the RC 
flag before I saw your message. I will unpublish them, delete tags, revert 
commits, etc. :(



On Thu, May 7, 2015 at 1:16 PM, Steven Gill  wrote:

> Looks like they just fixed the issue by using an older version of npm 
> to publish JSONStream 1.0.2 and 1.0.3. No need for a release! Woot!
>
> FTR, I don't think the hotfix would have caused any issues for us as 
> long as they kept browserify 10.1.2 around.
>
>
>
> On Thu, May 7, 2015 at 1:01 PM, Murat Sutunc 
> wrote:
>
>> Wait guys. I think we should hold on for a sec.
>>
>> There are 3 possible scenarios:
>> 1- We bump up our dependencies, latest version of Cordova is fixed 
>> but older ones remain broken.
>> 2- Browserify and/or module-deps can roll back (unpublish perhaps). 
>> Which will fix the issue for all cordova until npm makes the fix.
>> 3- NPM makes a quick fix.
>>
>> If we bump Cordova and browserify and module-deps decides to roll 
>> back, we'll be in trouble. I think the correct approach here is to 
>> talk with NPM and see what they suggest. If they commit on fixing 
>> this issue asap, browserify and module-deps can rollback and 
>> republish once everything is fixed. If you look at browserify and 
>> module-deps, using lowercase repos is a pretty recent change and 
>> there's probably less dependencies out there than Cordova.
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Thursday, May 7, 2015 12:47 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Rapid release of tools
>>
>> i'm working on getting the release ready
>>
>> On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:
>>
>> > +1 release off previous, with this one change only.
>> >
>> > On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
>> > 
>> > wrote:
>> > > I am thinking we release off our previous release branches with 
>> > > this one change. This needs to get out asap. I'm all for an 
>> > > accelerated
>> vote.
>> > >
>> > >
>> > >
>> > > On Thu, May 7, 2015 at 12:05 PM, Jesse 
>> wrote:
>> > >
>> > >> Given that all downstream distributions are broken currently, 
>> > >> can we do
>> > an
>> > >> accelerated vote?
>> > >> Are we introducing any other code that would slow us down? or 
>> > >> can we
>> > simply
>> > >> update+republish package.json files?
>> > >>
>> > >> @purplecabbage
>> > >> risingj.com
>> > >>
>> > >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
>> > >> 
>> > >> wrote:
>> > >>
>> > >> > I think we should do a quick release to get npm install 
>> > >> > cordova
>> > working
>> > >> > again asap.
>> > >> >
>> > >> > I have updated the browserify dependency on cordova-js which 
>> > >> > fixes the problem.
>> > >> >
>> > >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
>> > cordova-cli@5.0.1
>> > >> and
>> > >> > plugman@0.23.2 with the new dependency.
>> > >> >
>> > >>
>> >
>> > ---
>> > -- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > For additional commands, e-mail: dev-h...@cordova.apache.org
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [DISCUSS] Rapid release of tools

[Nikhil Khandelwal]

Yup. Thanks! Good to see cordova is installable again!

Thanks,
Nikhil


-Original Message-
From: Murat Sutunc [mailto:mura...@microsoft.com] 
Sent: Thursday, May 7, 2015 1:45 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Rapid release of tools

Ahh, thanks Steven for all the work! Glad to see Cordova working again!

-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Thursday, May 7, 2015 1:19 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Rapid release of tools

I have already published cordova-js@3.9.1 and cordova-lib@5.0.1 under the RC 
flag before I saw your message. I will unpublish them, delete tags, revert 
commits, etc. :(



On Thu, May 7, 2015 at 1:16 PM, Steven Gill  wrote:

> Looks like they just fixed the issue by using an older version of npm 
> to publish JSONStream 1.0.2 and 1.0.3. No need for a release! Woot!
>
> FTR, I don't think the hotfix would have caused any issues for us as 
> long as they kept browserify 10.1.2 around.
>
>
>
> On Thu, May 7, 2015 at 1:01 PM, Murat Sutunc 
> wrote:
>
>> Wait guys. I think we should hold on for a sec.
>>
>> There are 3 possible scenarios:
>> 1- We bump up our dependencies, latest version of Cordova is fixed 
>> but older ones remain broken.
>> 2- Browserify and/or module-deps can roll back (unpublish perhaps). 
>> Which will fix the issue for all cordova until npm makes the fix.
>> 3- NPM makes a quick fix.
>>
>> If we bump Cordova and browserify and module-deps decides to roll 
>> back, we'll be in trouble. I think the correct approach here is to 
>> talk with NPM and see what they suggest. If they commit on fixing 
>> this issue asap, browserify and module-deps can rollback and 
>> republish once everything is fixed. If you look at browserify and 
>> module-deps, using lowercase repos is a pretty recent change and 
>> there's probably less dependencies out there than Cordova.
>>
>> -Original Message-
>> From: Steven Gill [mailto:stevengil...@gmail.com]
>> Sent: Thursday, May 7, 2015 12:47 PM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Rapid release of tools
>>
>> i'm working on getting the release ready
>>
>> On Thu, May 7, 2015 at 12:37 PM, Shazron  wrote:
>>
>> > +1 release off previous, with this one change only.
>> >
>> > On Thu, May 7, 2015 at 12:07 PM, Steven Gill 
>> > 
>> > wrote:
>> > > I am thinking we release off our previous release branches with 
>> > > this one change. This needs to get out asap. I'm all for an 
>> > > accelerated
>> vote.
>> > >
>> > >
>> > >
>> > > On Thu, May 7, 2015 at 12:05 PM, Jesse 
>> wrote:
>> > >
>> > >> Given that all downstream distributions are broken currently, 
>> > >> can we do
>> > an
>> > >> accelerated vote?
>> > >> Are we introducing any other code that would slow us down? or 
>> > >> can we
>> > simply
>> > >> update+republish package.json files?
>> > >>
>> > >> @purplecabbage
>> > >> risingj.com
>> > >>
>> > >> On Thu, May 7, 2015 at 12:01 PM, Steven Gill 
>> > >> 
>> > >> wrote:
>> > >>
>> > >> > I think we should do a quick release to get npm install 
>> > >> > cordova
>> > working
>> > >> > again asap.
>> > >> >
>> > >> > I have updated the browserify dependency on cordova-js which 
>> > >> > fixes the problem.
>> > >> >
>> > >> > Need to release cordova-js@3.9.1, cordova-lib@5.0.1,
>> > cordova-cli@5.0.1
>> > >> and
>> > >> > plugman@0.23.2 with the new dependency.
>> > >> >
>> > >>
>> >
>> > ---
>> > -- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > For additional commands, e-mail: dev-h...@cordova.apache.org
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: Orientation preference now updates value...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-lib/pull/207#issuecomment-100025000
  
Hi Rachel - can you update the title with a prefix of CB-6462 CB-6026 (to 
enable some auto-tracking with JIRA) 


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Also moving to a new team

[Brian LeRoux]

really appreciate the level headed contributions to our community and code
Marcel & Staci; glad to have had the chance to work with you both!

On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard  wrote:

> Staci Cooper and I are also moving to new positions. There already are
> backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> seeing more of them here as time moves forward, joining Edna Morales.
>
> This has been an absolutely awesome group to work with. You're smart,
> talented, passionate, and you deliver. I can't say that I had a single bad
> experience here. I will definitely miss it, I hope our paths cross again.
> Best wishes!
>
> I may be tempted to dabble here in my off-hours. ;-)
>
> -- Marcel Kinard
>
> > On May 5, 2015, at 11:15 AM, Andrew Grieve  wrote:
> >
> > As with Michal, you'll be seeing less of me around. My new full-time
> > project will be on the Android port of Chrome.
> >
> > Just want to make it clear that us moving to new teams has nothing to do
> > with a lack of faith in the project, but rather is due to needing a
> change
> > of scenery and exciting new projects becoming available here.
> >
> > I'm super excited to see a new wave of committers joining the project!
> The
> > momentum has certainly picked up:
> > - Cordova-android 4.0.0 was huge
> > - Plugins to npm was huge
> > - Win10 and wkwebview will be massive launches as well!
> >
> > Great time for Cordova! (or a bad one... you know... if you're measuring
> > against the goal of becoming obsolete :P)
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

RE: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Murat Sutunc]

We seem to have some files missing the Apache license:
cordova-plugin-camera/tests/ios/CDVCameraTest/CDVCameraLibTests/Info.plist
cordova-plugin-vibration/src/blackberry10/native/.cproject
 cordova-plugin-vibration/src/blackberry10/native/.project
cordova-plugin-vibration/src/windows/Vibration/Vibration.cs
cordova-plugin-vibration/src/windows/Vibration/Vibration.csproj
cordova-plugin-vibration/src/windows/Vibration/Properties/AssemblyInfo.cs

-Original Message-
From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com] 
Sent: Thursday, May 7, 2015 1:20 PM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, 
device-motion)

* Verified signatures and hashes
* Verified tags
* Verified plugins added correctly to blank app
* Verified blank app can be successfully ran and built
* Ran smoke testing of mobilespec app
* Performed manual ad-hoc testing
* Verified Release Notes

I vote +1.

Thanks,
Nikhil


-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Thursday, May 7, 2015 12:57 PM
To: dev@cordova.apache.org
Subject: Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, 
device-motion)

+1
* coho verify-archive
* unpacked and verified each plugin could be installed, and run on ios
* manually verified version numbers throughout all package.json and plugin.xml 
files

@purplecabbage
risingj.com

On Wed, May 6, 2015 at 5:42 PM, Steven Gill  wrote:

> Please review and vote on the release of this plugins release by 
> replying to this email (and keep discussion on the DISCUSS thread)
>
> Release issue: https://issues.apache.org/jira/browse/CB-8959
>
> The plugins have been published to
> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
>
> The packages were published from their corresponding git tags:
> cordova-plugin-camera: 1.1.0 (19feee9cb0)
> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
> cordova-plugin-dialogs: 1.1.0 (439372988b)
> cordova-plugin-vibration: 1.1.0 (4d316e2555)
>
> Upon a successful vote I will upload the archives to dist/, upload 
> them to npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> .md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and 
> subdependencies have Apache-compatible licenses
>
B CB  [  
X  ܚX KK[XZ[
 ] ][  X  ܚX P ܙݘK \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 ] Z[ ܙݘK \X K ܙ B

[GitHub] cordova-medic pull request: CB-8961 Killing more Android tasks on ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-medic/pull/52


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Also moving to a new team

[Joe Bowser]

+1 to that.  Good luck to you both on what you're working on next.

On Thu, May 7, 2015 at 2:29 PM Brian LeRoux  wrote:

> really appreciate the level headed contributions to our community and code
> Marcel & Staci; glad to have had the chance to work with you both!
>
> On Thu, May 7, 2015 at 11:04 AM, Marcel Kinard  wrote:
>
> > Staci Cooper and I are also moving to new positions. There already are
> > backfills here coming up to speed: Karen Tran and James Dubee. You'll be
> > seeing more of them here as time moves forward, joining Edna Morales.
> >
> > This has been an absolutely awesome group to work with. You're smart,
> > talented, passionate, and you deliver. I can't say that I had a single
> bad
> > experience here. I will definitely miss it, I hope our paths cross again.
> > Best wishes!
> >
> > I may be tempted to dabble here in my off-hours. ;-)
> >
> > -- Marcel Kinard
> >
> > > On May 5, 2015, at 11:15 AM, Andrew Grieve 
> wrote:
> > >
> > > As with Michal, you'll be seeing less of me around. My new full-time
> > > project will be on the Android port of Chrome.
> > >
> > > Just want to make it clear that us moving to new teams has nothing to
> do
> > > with a lack of faith in the project, but rather is due to needing a
> > change
> > > of scenery and exciting new projects becoming available here.
> > >
> > > I'm super excited to see a new wave of committers joining the project!
> > The
> > > momentum has certainly picked up:
> > > - Cordova-android 4.0.0 was huge
> > > - Plugins to npm was huge
> > > - Win10 and wkwebview will be massive launches as well!
> > >
> > > Great time for Cordova! (or a bad one... you know... if you're
> measuring
> > > against the goal of becoming obsolete :P)
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

[GitHub] cordova-lib pull request: CB-6462 CB-6026 Orientation preference n...

[rachel-carvalho]

Github user rachel-carvalho commented on the pull request:

https://github.com/apache/cordova-lib/pull/207#issuecomment-100033206
  
Done!


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Shazron]

See guidelines below.
Of all the files, I think Vibration.cs is clearly not excepted.

==

http://www.apache.org/legal/src-headers.html

WHAT FILES IN AN APACHE RELEASE DO NOT REQUIRE A LICENSE HEADER?

A file without any degree of creativity in either its literal elements
or its structure is not protected by copyright law; therefore, such a
file does not require a license header. If in doubt about the extent
of the file's creativity, add the license header to the file.

On Thu, May 7, 2015 at 2:37 PM, Murat Sutunc  wrote:
> We seem to have some files missing the Apache license:
> cordova-plugin-camera/tests/ios/CDVCameraTest/CDVCameraLibTests/Info.plist
> cordova-plugin-vibration/src/blackberry10/native/.cproject
>  cordova-plugin-vibration/src/blackberry10/native/.project
> cordova-plugin-vibration/src/windows/Vibration/Vibration.cs
> cordova-plugin-vibration/src/windows/Vibration/Vibration.csproj
> cordova-plugin-vibration/src/windows/Vibration/Properties/AssemblyInfo.cs
>
> -Original Message-
> From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
> Sent: Thursday, May 7, 2015 1:20 PM
> To: dev@cordova.apache.org
> Subject: RE: [VOTE] Plugins Release (camera, file-transfer, dialogs, 
> vibration, device-motion)
>
> * Verified signatures and hashes
> * Verified tags
> * Verified plugins added correctly to blank app
> * Verified blank app can be successfully ran and built
> * Ran smoke testing of mobilespec app
> * Performed manual ad-hoc testing
> * Verified Release Notes
>
> I vote +1.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Thursday, May 7, 2015 12:57 PM
> To: dev@cordova.apache.org
> Subject: Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, 
> vibration, device-motion)
>
> +1
> * coho verify-archive
> * unpacked and verified each plugin could be installed, and run on ios
> * manually verified version numbers throughout all package.json and 
> plugin.xml files
>
> @purplecabbage
> risingj.com
>
> On Wed, May 6, 2015 at 5:42 PM, Steven Gill  wrote:
>
>> Please review and vote on the release of this plugins release by
>> replying to this email (and keep discussion on the DISCUSS thread)
>>
>> Release issue: https://issues.apache.org/jira/browse/CB-8959
>>
>> The plugins have been published to
>> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
>>
>> The packages were published from their corresponding git tags:
>> cordova-plugin-camera: 1.1.0 (19feee9cb0)
>> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
>> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
>> cordova-plugin-dialogs: 1.1.0 (439372988b)
>> cordova-plugin-vibration: 1.1.0 (4d316e2555)
>>
>> Upon a successful vote I will upload the archives to dist/, upload
>> them to npm, and post the corresponding blog post.
>>
>> Voting guidelines:
>> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
>> .md
>>
>> Voting will go on for a minimum of 48 hours.
>>
>> I vote +1:
>> * Ran coho audit-license-headers over the relevant repos
>> * Ran coho check-license to ensure all dependencies and
>> subdependencies have Apache-compatible licenses
>>
>  B CB
> [  X  ܚX K  K[XZ[
>] ][  X  ܚX P  ܙ ݘK \ X  K ܙ B  ܈ Y  ] [ۘ[[X[ K[XZ[
>] Z [ܙ ݘK \ X  K ܙ B

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-6462 CB-6026 Orientation preference n...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-lib/pull/207#issuecomment-100042422
  
CB-8783 affects iPad as well, by inspecting the existing code (not yours).


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Jesse]

Updated all of those.
I only think the vibration plugin would need a repak.

@purplecabbage
risingj.com

On Thu, May 7, 2015 at 3:01 PM, Shazron  wrote:

> See guidelines below.
> Of all the files, I think Vibration.cs is clearly not excepted.
>
> ==
>
> http://www.apache.org/legal/src-headers.html
>
> WHAT FILES IN AN APACHE RELEASE DO NOT REQUIRE A LICENSE HEADER?
>
> A file without any degree of creativity in either its literal elements
> or its structure is not protected by copyright law; therefore, such a
> file does not require a license header. If in doubt about the extent
> of the file's creativity, add the license header to the file.
>
> On Thu, May 7, 2015 at 2:37 PM, Murat Sutunc 
> wrote:
> > We seem to have some files missing the Apache license:
> >
> cordova-plugin-camera/tests/ios/CDVCameraTest/CDVCameraLibTests/Info.plist
> > cordova-plugin-vibration/src/blackberry10/native/.cproject
> >  cordova-plugin-vibration/src/blackberry10/native/.project
> > cordova-plugin-vibration/src/windows/Vibration/Vibration.cs
> > cordova-plugin-vibration/src/windows/Vibration/Vibration.csproj
> > cordova-plugin-vibration/src/windows/Vibration/Properties/AssemblyInfo.cs
> >
> > -Original Message-
> > From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
> > Sent: Thursday, May 7, 2015 1:20 PM
> > To: dev@cordova.apache.org
> > Subject: RE: [VOTE] Plugins Release (camera, file-transfer, dialogs,
> vibration, device-motion)
> >
> > * Verified signatures and hashes
> > * Verified tags
> > * Verified plugins added correctly to blank app
> > * Verified blank app can be successfully ran and built
> > * Ran smoke testing of mobilespec app
> > * Performed manual ad-hoc testing
> > * Verified Release Notes
> >
> > I vote +1.
> >
> > Thanks,
> > Nikhil
> >
> >
> > -Original Message-
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Thursday, May 7, 2015 12:57 PM
> > To: dev@cordova.apache.org
> > Subject: Re: [VOTE] Plugins Release (camera, file-transfer, dialogs,
> vibration, device-motion)
> >
> > +1
> > * coho verify-archive
> > * unpacked and verified each plugin could be installed, and run on ios
> > * manually verified version numbers throughout all package.json and
> plugin.xml files
> >
> > @purplecabbage
> > risingj.com
> >
> > On Wed, May 6, 2015 at 5:42 PM, Steven Gill 
> wrote:
> >
> >> Please review and vote on the release of this plugins release by
> >> replying to this email (and keep discussion on the DISCUSS thread)
> >>
> >> Release issue: https://issues.apache.org/jira/browse/CB-8959
> >>
> >> The plugins have been published to
> >> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
> >>
> >> The packages were published from their corresponding git tags:
> >> cordova-plugin-camera: 1.1.0 (19feee9cb0)
> >> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
> >> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
> >> cordova-plugin-dialogs: 1.1.0 (439372988b)
> >> cordova-plugin-vibration: 1.1.0 (4d316e2555)
> >>
> >> Upon a successful vote I will upload the archives to dist/, upload
> >> them to npm, and post the corresponding blog post.
> >>
> >> Voting guidelines:
> >> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> >> .md
> >>
> >> Voting will go on for a minimum of 48 hours.
> >>
> >> I vote +1:
> >> * Ran coho audit-license-headers over the relevant repos
> >> * Ran coho check-license to ensure all dependencies and
> >> subdependencies have Apache-compatible licenses
> >>
> >  B
> CB
> [  X  ܚX K  K[XZ[
> >] ][  X  ܚX P  ܙ ݘK \ X  K ܙ B  ܈ Y  ] [ۘ[[X[ K[XZ[
> >] Z [ܙ ݘK \ X  K ܙ B
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

[GitHub] cordova-plugin-splashscreen pull request: CB-8988: Fix rotation on...

[dpolivy]

GitHub user dpolivy opened a pull request:

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

CB-8988: Fix rotation on iOS/iPad

The viewController.interfaceOrientation passed to getImageName has not
yet been updated with the new orientation, even when the frame/bounds
change event has fired. Thus, the plugin never actually loads the
correct image for the new orientation. Instead, it poorly scales the
existing image.

This fix uses the statusBarOrientation property of the UIApplication
object to detect the actual orientation, and correctly load the right
image.

Fixes https://issues.apache.org/jira/browse/CB-8988

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

$ git pull https://github.com/dpolivy/cordova-plugin-splashscreen CB8988

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

https://github.com/apache/cordova-plugin-splashscreen/pull/46.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 #46


commit 4df490b4d935ffd43904dda1726a790372c64d92
Author: Dan Polivy 
Date:   2015-05-07T23:37:02Z

CB-8988: Fix rotation on iOS/iPad

The viewController.interfaceOrientation passed to getImageName has not
yet been updated with the new orientation, even when the frame/bounds
change event has fired. Thus, the plugin never actually loads the
correct image for the new orientation. Instead, it poorly scales the
existing image.

This fix uses the statusBarOrientation property of the UIApplication
object to detect the actual orientation, and correctly load the right
image.




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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-splashscreen pull request: CB-8988: Fix rotation on...

[dpolivy]

Github user dpolivy commented on the pull request:


https://github.com/apache/cordova-plugin-splashscreen/pull/46#issuecomment-100047179
  
@shazron Can you please review & merge?


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-camera pull request: CB-7667 iOS8: Handle case wher...

[dpolivy]

Github user dpolivy commented on the pull request:


https://github.com/apache/cordova-plugin-camera/pull/49#issuecomment-100047309
  
@shazron Any possibility of a review & merge for the next plugin release?


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Plugins Release (camera, file-transfer, dialogs, vibration, device-motion)

[Steven Gill]

This vote does not include the vibration plugin anymore. The other 4
plugins are fine. I am starting a new thread for the vibration plugin.



On Thu, May 7, 2015 at 4:05 PM, Jesse  wrote:

> Updated all of those.
> I only think the vibration plugin would need a repak.
>
> @purplecabbage
> risingj.com
>
> On Thu, May 7, 2015 at 3:01 PM, Shazron  wrote:
>
> > See guidelines below.
> > Of all the files, I think Vibration.cs is clearly not excepted.
> >
> > ==
> >
> > http://www.apache.org/legal/src-headers.html
> >
> > WHAT FILES IN AN APACHE RELEASE DO NOT REQUIRE A LICENSE HEADER?
> >
> > A file without any degree of creativity in either its literal elements
> > or its structure is not protected by copyright law; therefore, such a
> > file does not require a license header. If in doubt about the extent
> > of the file's creativity, add the license header to the file.
> >
> > On Thu, May 7, 2015 at 2:37 PM, Murat Sutunc 
> > wrote:
> > > We seem to have some files missing the Apache license:
> > >
> >
> cordova-plugin-camera/tests/ios/CDVCameraTest/CDVCameraLibTests/Info.plist
> > > cordova-plugin-vibration/src/blackberry10/native/.cproject
> > >  cordova-plugin-vibration/src/blackberry10/native/.project
> > > cordova-plugin-vibration/src/windows/Vibration/Vibration.cs
> > > cordova-plugin-vibration/src/windows/Vibration/Vibration.csproj
> > >
> cordova-plugin-vibration/src/windows/Vibration/Properties/AssemblyInfo.cs
> > >
> > > -Original Message-
> > > From: Nikhil Khandelwal [mailto:nikhi...@microsoft.com]
> > > Sent: Thursday, May 7, 2015 1:20 PM
> > > To: dev@cordova.apache.org
> > > Subject: RE: [VOTE] Plugins Release (camera, file-transfer, dialogs,
> > vibration, device-motion)
> > >
> > > * Verified signatures and hashes
> > > * Verified tags
> > > * Verified plugins added correctly to blank app
> > > * Verified blank app can be successfully ran and built
> > > * Ran smoke testing of mobilespec app
> > > * Performed manual ad-hoc testing
> > > * Verified Release Notes
> > >
> > > I vote +1.
> > >
> > > Thanks,
> > > Nikhil
> > >
> > >
> > > -Original Message-
> > > From: Jesse [mailto:purplecabb...@gmail.com]
> > > Sent: Thursday, May 7, 2015 12:57 PM
> > > To: dev@cordova.apache.org
> > > Subject: Re: [VOTE] Plugins Release (camera, file-transfer, dialogs,
> > vibration, device-motion)
> > >
> > > +1
> > > * coho verify-archive
> > > * unpacked and verified each plugin could be installed, and run on ios
> > > * manually verified version numbers throughout all package.json and
> > plugin.xml files
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> > > On Wed, May 6, 2015 at 5:42 PM, Steven Gill 
> > wrote:
> > >
> > >> Please review and vote on the release of this plugins release by
> > >> replying to this email (and keep discussion on the DISCUSS thread)
> > >>
> > >> Release issue: https://issues.apache.org/jira/browse/CB-8959
> > >>
> > >> The plugins have been published to
> > >> dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/
> > >>
> > >> The packages were published from their corresponding git tags:
> > >> cordova-plugin-camera: 1.1.0 (19feee9cb0)
> > >> cordova-plugin-file-transfer: 1.1.0 (e251db5cac)
> > >> cordova-plugin-device-motion: 1.1.0 (7d52b8457d)
> > >> cordova-plugin-dialogs: 1.1.0 (439372988b)
> > >> cordova-plugin-vibration: 1.1.0 (4d316e2555)
> > >>
> > >> Upon a successful vote I will upload the archives to dist/, upload
> > >> them to npm, and post the corresponding blog post.
> > >>
> > >> Voting guidelines:
> > >>
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting
> > >> .md
> > >>
> > >> Voting will go on for a minimum of 48 hours.
> > >>
> > >> I vote +1:
> > >> * Ran coho audit-license-headers over the relevant repos
> > >> * Ran coho check-license to ensure all dependencies and
> > >> subdependencies have Apache-compatible licenses
> > >>
> > >  B
> > CB
> > [  X  ܚX K  K[XZ[
> > >] ][  X  ܚX P  ܙ ݘK \ X  K ܙ B  ܈ Y  ] [ۘ[[X[ K[XZ[
> > >] Z [ܙ ݘK \ X  K ܙ B
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

[VOTE] cordova-plugin-vibration release

[Steven Gill]

Please review and vote on the release of cordova-plugin-vibration release
by replying to this email (and keep discussion on the DISCUSS thread)

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

The plugins have been published to
dist/dev:https://dist.apache.org/repos/dist/dev/cordova/CB-8959/

The packages were published from their corresponding git tags:
cordova-plugin-vibration: 1.1.0 (81729f0f5c)

Upon a successful vote I will upload the archives to dist/ and upload it to npm.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md

Voting will go on for a minimum of 48 hours.

I vote +1:

[GitHub] cordova-plugin-splashscreen pull request: CB-3562: Disable screen ...

[dpolivy]

GitHub user dpolivy opened a pull request:

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

CB-3562: Disable screen rotation for iPhone when splash screen is shown 
(updated)

This is an updated port of emarashliev's fix for CB-3562, as this bug still 
exists. The original PR #14 seems to be dead, however. I ported these changes 
over to the latest branch of the plugin, and made some minor adjustments to 
avoid deprecated functions.

@shazron @agrieve Given the discussion in the previous PR, hopefully this 
can be reviewed and incorporated quickly.

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

$ git pull https://github.com/dpolivy/cordova-plugin-splashscreen CB3562

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

https://github.com/apache/cordova-plugin-splashscreen/pull/47.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 #47


commit 545b0a81139dd48accc4c25ccc8c8b2052635928
Author: Emil Marashliev 
Date:   2014-02-19T14:05:34Z

CB-3562 Disable screen rotation for iPhone when splash screen is shown.

commit b6e3023f31063f4d6204355e6b13c348180cf603
Author: Dan Polivy 
Date:   2015-05-08T00:35:10Z

CB-3562: Disable screen rotation for iPhone when splash screen is shown.

This is a port of emarashliev's original fix for CB-3562, cleaned up
to avoid deprecated functions.

Merge branch 'master' of 
https://github.com/emarashliev/cordova-plugin-splashscreen into CB3562




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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Cordova 5.0 user feedback - move to npm & whitelist plugin

[Steven Gill]

(1) older versions of our docs point to plugins.cordova.io for plugin
documentation. We haven't pointed people to github for plugin docs. Those
docs are accurate with the ID of the plugin. Adding a section to the readme
about needing cordova 5+ isn't a bad idea.

The plan is to switch our tools to grab from npm first and CPR second. I
believe we discussed doing this around the time CPR goes read only. Giving
IDE's and people using older versions a chance to upgrade.

We can publish updated plugins to CPR, but it is going to be quite a bit of
work. I created old-id branches for our core plugins that revert the
commits changing the ID and the commits where I change internal plugin
references from org.apache.cordova.* to cordova-plugin-*. It was a fairly
large change. The reason for the major jump was the plugin id change. I'd
recommend them sticking the versioning they are on instead of copying the
version of the npm series. The major version bump wasn't due to a change in
functionality in the plugins themselves.

If we want to release updated plugins to CPR, someone will need to do the
work to cherry-pick the new commits into old-id and do a separate vote for
them.


(2) It is a fairly recent change. Any new app made with cordova-cli 5+ will
auto include the whitelist plugin due to the hello world config.xml
including it as a dependency. I think we need to document it more and make
more noise within the community about it. iOS 4.0 will also require the
whitelist plugin when it gets released. The more prepared we are, the
better.

As for re-enabling network access by default, I wasn't really part of the
original thread so I will leave it to the people who were to discuss that
further.

On Thu, May 7, 2015 at 8:55 AM, Nikhil Khandelwal 
wrote:

> There is a bunch of confusion with Cordova 5.0 users because of these two
> changes:
>
> 1. Move to npm for plugins (There have been multiple PRs trying to update
> plugin docs to reference the old id instead of the new one - because people
> are still using the old version of the CLI)
>
> 2. No network access in Android 4.0 without whitelist plugin:
>
>   - https://issues.apache.org/jira/browse/CB-8969
>
>   -
> http://stackoverflow.com/questions/29735597/cordova-5-0-0-android-app-can-not-connect-to-internet-using-android-4-0-0
>
> -
> http://stackoverflow.com/questions/30060534/ajax-requests-fail-after-upgrading-to-cordova-5-0-cordova-android4-0
>
>
>
> I think for the (1), I suggest we do the following:
>
> 1.   Update the plugin documentation that the old id can be used for
> older CLI versions.
>
> 2.   Either update the CPM with 1.0 versions of the plugins or have
> the CLI get core plugins from npm first then CPR even with the old id.
> Using the old id because they were hardcoded in IDEs etc, devs are getting
> older version of the plugins.
>
>
>
> For (2), I think we should re-visit making whitelist part of the Android
> platform again or some other way of enabling network access by default. No
> network access (XHR) for a platform by default is a big change that's not
> well understood and not necessarily more secure. I'm new to this, but I did
> not fully understood the goals of moving the whitelisting to a plugin
> instead of it being part of the core.
>
>
> Thanks,
> Nikhil
>

Re: No Readme for plugin packages on npm

[Steven Gill]

https://github.com/npm/marky-markdown/issues/42

I will try to see if I can fix marky-markdown myself. If it isn't easy, we
could just update our readme's and republish.

On Wed, May 6, 2015 at 10:39 PM, Nikhil Khandelwal 
wrote:

> Thanks, Steven! Do you have a pointer to the issue? In case they can't get
> do this soon - perhaps we should explore a workaround.
>
> -Nikhil
>
> -Original Message-
> From: Steven Gill [mailto:stevengil...@gmail.com]
> Sent: Thursday, April 23, 2015 6:34 PM
> To: dev@cordova.apache.org
> Subject: Re: No Readme for plugin packages on npm
>
> I filed the issue a few days ago with npm. They are working on fixing it.
> The parser is struggling with html comments On Apr 23, 2015 6:14 PM,
> "Nikhil Khandelwal"  wrote:
>
> > It looks like npm cannot find the readme for plugin packages:
> > https://www.npmjs.com/package/cordova-plugin-battery-status
> >
> > Github can find it just fine though:
> > https://github.com/apache/cordova-plugin-battery-status
> >
> > Thanks,
> > Nikhil
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

[GitHub] cordova-lib pull request: CB-6462 CB-6026 Orientation preference n...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-lib/pull/207#issuecomment-100069439
  
Integrated: 
https://git1-us-west.apache.org/repos/asf?p=cordova-lib.git;a=commit;h=93ab6b61
You can close this issue now, 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.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Document iOS specific callback for orie...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/276#issuecomment-100075104
  
That JS function shouldRotateToOrientation will not be supported in 
cordova-ios 4.0.x.
This is because of the pluggable webview support. The CDVWebViewEngine 
interface calls for an async call to JavaScript now (WKWebView's function to 
call into JS is async).

Because this call is async, the supportedOrientations selector that is 
called by the CDVViewController synchronously, can't use the async function 
above.





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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Document iOS specific callback for orie...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/276#issuecomment-100076514
  
I'm not in favour of adding yet another preference. 

If we look at the Apple docs: 

https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW10

Setting no values, implicitly sets the orientation to Portrait. Thus 
"default" === "portrait" here. I'm not sure this is really useful for users, 
especially if they don't know what "default" is (but that's a matter of 
documentation). Of course this varies by platform.

I would leave default as implemented by @mmrko -- since it is technically 
correct -- but add a new preference "all" which is unambiguously clear.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Document iOS specific callback for orie...

[shazron]

Github user shazron commented on the pull request:

https://github.com/apache/cordova-docs/pull/276#issuecomment-100076679
  
@nikhilkh can you edit the title to have a prefix of CB-8783 to enable auto 
JIRA tracking.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Cloning FirefoxOS repo fails on Windows

[Dmitry Blotsky]

Hi list,

I'm trying to clone Cordova FirefoxOS on Windows, and it's failing for me 
because of name-too-long errors. What is our workaround for this?

Kindly,
Dmitry

[GitHub] cordova-medic pull request: CB-8936 Gathering logs for Android

[dblotsky]

Github user dblotsky commented on a diff in the pull request:

https://github.com/apache/cordova-medic/pull/53#discussion_r29915081
  
--- Diff: medic/medic-log.js ---
@@ -0,0 +1,60 @@
+#!/usr/bin/env node
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+/* jshint node: true */
+
+"use strict";
+
+var fs = require("fs");
+
+var shelljs  = require("shelljs");
+var optimist = require("optimist");
+var util = require("../lib/util");
+
+// main
+function main() {
+
+// shell config
+shelljs.config.fatal  = false;
+shelljs.config.silent = false;
+
+// command-specific args
+var argv = optimist
+.usage("Usage: $0 {platform}")
+.argv;
--- End diff --

Please `demand()` the `platform` argument.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-8936 Gathering logs for Android

[dblotsky]

Github user dblotsky commented on a diff in the pull request:

https://github.com/apache/cordova-medic/pull/53#discussion_r29915107
  
--- Diff: medic/medic-log.js ---
@@ -0,0 +1,60 @@
+#!/usr/bin/env node
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+/* jshint node: true */
+
+"use strict";
+
+var fs = require("fs");
+
+var shelljs  = require("shelljs");
+var optimist = require("optimist");
+var util = require("../lib/util");
+
+// main
+function main() {
+
+// shell config
+shelljs.config.fatal  = false;
+shelljs.config.silent = false;
+
+// command-specific args
+var argv = optimist
+.usage("Usage: $0 {platform}")
+.argv;
+
+switch (argv.platform) {
+case util.ANDROID:
+var cmd = "adb logcat -d";
+console.log("executing " + cmd);
+shelljs.exec(cmd, function(code, output) {
+if (code > 0) {
+fatal('Failed to run logcat command.');
--- End diff --

I was about to merge and did a test, and caught a small bug. It's now 
`util.fatal`.


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

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org