[jira] [Resolved] (CB-5611) battery-status
[ https://issues.apache.org/jira/browse/CB-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zalewa resolved CB-5611. -- Resolution: Fixed Merged to master battery-status -- Key: CB-5611 URL: https://issues.apache.org/jira/browse/CB-5611 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: Steve Gill Assignee: Rodrigo Silveira -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zalewa resolved CB-6718.
--
Resolution: Fixed
The string is fixed and the coho is changed so it won't happen in the future
cordova firefox reports wrong version
-
Key: CB-6718
URL: https://issues.apache.org/jira/browse/CB-6718
Project: Apache Cordova
Issue Type: Bug
Components: FirefoxOS
Affects Versions: 3.5.0
Environment: MacOSX
Reporter: Carlos Santana
While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
should report 3.5.0
Steps to replicate
Install cordova cli 3.5.0-0.2.4
{code}
$ ../../node_modules/.bin/cordova -v
3.5.0-0.2.4
$ ./node_modules/.bin/cordova create firefox350/newProj
Creating a new cordova project with name HelloCordova and id
io.cordova.hellocordova at location
/Users/csantana23/Documents/cordova/firefox350/newProj
Downloading cordova library for www...
Download complete
/Users/csantana23/Documents/cordova/firefox350/newProj
$ ../../node_modules/.bin/cordova platform add firefoxos
Downloading cordova library for firefoxos...
Download complete
Creating firefoxos project...
Creating Firefox OS project
Project Path platforms/firefoxos
Package Name io.cordova.hellocordova
Project Name HelloCordova
/Users/csantana23/Documents/cordova/firefox350/newProj
$ ../../node_modules/.bin/cordova platform ls
Installed platforms: firefoxos 3.4.0-dev
Available platforms: amazon-fireos, android, blackberry10, ios
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (CB-6692) Launching the camera on Android fails with the Play Store version of (Google) Camera.
[
https://issues.apache.org/jira/browse/CB-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Vermeule closed CB-6692.
--
Resolution: Invalid
The error occurred due to an error on my side. I accidentally bound the event
of opening the camera more than once.
Launching the camera on Android fails with the Play Store version of (Google)
Camera.
-
Key: CB-6692
URL: https://issues.apache.org/jira/browse/CB-6692
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 3.4.0
Reporter: Björn Vermeule
Attachments: Screenshot_2014-05-14-16-58-40.png
Google recently released the Android Camera as an app in the Play Store
([link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]).
It seems that the most recent version of Google Camera prevents Cordova to
launch/connect to the app.
When removing Google Camera (and thus reverting to the system Camera) Cordova
can successfully take pictures. Cordova fails when I reinstall Google Camera
again.
Cordova fails with the error message Can't connect to the camera. (see
attached screenshot). The camera does start and I am able to take pictures
(from the camera's point of view) but Cordova will always fail and call the
error handler.
JavaScript code I'm using to launch the camera:
{code:JavaScript}
navigator.camera.getPicture(
function(imageData) {
$('.taken-image').attr('src', imageData);
},
function() {
alert('Picture has not been taken ...');
}, {
quality: 50,
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.CAMERA
});
{code}
I've tested this on a Nexus 4 and 5.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6727) build.xml in Android SDK directory is not found when new SDK installed or project moved to another computer
Ceyhun Can ÜLKER created CB-6727: Summary: build.xml in Android SDK directory is not found when new SDK installed or project moved to another computer Key: CB-6727 URL: https://issues.apache.org/jira/browse/CB-6727 Project: Apache Cordova Issue Type: Improvement Components: Android Affects Versions: 3.4.0 Environment: Windows 8.1 (possibly other operating systems as well) Reporter: Ceyhun Can ÜLKER Priority: Minor When I moved my project to another computer my cordova project stopped building. Error was due to the imported ant buildfile of Android SDK was not found. I saw that local.properties file in platforms/android folder contains a fixed path, and thought that if I comment it out, sdk.dir would be taken from environment; but it wasn't the case. After extensive searching and looking through verbose output, I found out that platforms/android/CordovaLib contains another properties file. After changing the path there problem solved. My suggestion to this problem would be that, since these are generated file and not really meant to be changed, defaults should remain in those files but they should be overridden by environment variables. I guess this would solve this portability issue with respect to development environment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6570) mobile-spec has inline JavaScript which is forbidden for Firefox OS privileged apps
[ https://issues.apache.org/jira/browse/CB-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004625#comment-14004625 ] Piotr Zalewa commented on CB-6570: -- As far as I know right now there is a tendency to move tests to plugins. Has this pull request became irrelevant? mobile-spec has inline JavaScript which is forbidden for Firefox OS privileged apps --- Key: CB-6570 URL: https://issues.apache.org/jira/browse/CB-6570 Project: Apache Cordova Issue Type: Bug Components: FirefoxOS, mobile-spec Reporter: Piotr Zalewa Assignee: Piotr Zalewa -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5816) FirefoxOS - add build script
[ https://issues.apache.org/jira/browse/CB-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zalewa resolved CB-5816. -- Resolution: Fixed FirefoxOS - add build script Key: CB-5816 URL: https://issues.apache.org/jira/browse/CB-5816 Project: Apache Cordova Issue Type: Bug Components: FirefoxOS Reporter: Axel Nennker run: cordova build firefoxos output: Generating config.xml from defaults for platform firefoxos Preparing firefoxos project Compiling app on platform firefoxos via command /project/platforms/firefoxos/cordova/build events.js:72 throw er; // Unhandled 'error' event ^ Error: spawn ENOENT at errnoException (child_process.js:980:11) at Process.ChildProcess._handle.onexit (child_process.js:771:34) project$ expected output: nothing - platforms/firefoxos/cordova/build does not exist so the cordova build firefoxos command fails. Please add a build script (although it does nothing) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-4550) Add ./cordova/build project level script
[
https://issues.apache.org/jira/browse/CB-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zalewa closed CB-4550.
Resolution: Duplicate
Add ./cordova/build project level script
Key: CB-4550
URL: https://issues.apache.org/jira/browse/CB-4550
Project: Apache Cordova
Issue Type: Sub-task
Components: FirefoxOS
Reporter: Steve Gill
{code}
build [--debug] [--release]
{code}
Builds the application and compiles to the platform's appropriate binary
format.
By default builds a debug release:
{code}
build --debug
{code}
Supports building a release (possibly signed) build using:
{code}
build --release
{code}
Implicitly calls {{./cordova/clean}} first.
If both {{release}} and {{debug}} parameters are specified, error out with
exit code 2 and an appropriate error message.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6200) plugman has broken all plugins for firefoxos
[ https://issues.apache.org/jira/browse/CB-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zalewa resolved CB-6200. -- Resolution: Fixed plugman has broken all plugins for firefoxos Key: CB-6200 URL: https://issues.apache.org/jira/browse/CB-6200 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: James Long Somehow the firefoxos code in plugman got broken and all `plugin add` commands throw this error: Fetching plugin org.apache.cordova.camera via plugin registry Installing org.apache.cordova.camera (firefoxos) ReferenceError: xml_helpers is not defined This line here uses `xml_helpers` but it's not defined: https://github.com/apache/cordova-plugman/blob/master/src/platforms/firefoxos.js#L25. This looks like it's in the live version. Are all of our plugins broken for cordova and phonegap? This person fixed it with this PR. Please merge it: https://github.com/apache/cordova-plugman/pull/61 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-5271) cordova prepare firefoxos comes back with useless information when the platform is not installed
[
https://issues.apache.org/jira/browse/CB-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Zalewa closed CB-5271.
Resolution: Fixed
Not happening in 3.4.x
cordova prepare firefoxos comes back with useless information when the
platform is not installed
Key: CB-5271
URL: https://issues.apache.org/jira/browse/CB-5271
Project: Apache Cordova
Issue Type: Bug
Components: FirefoxOS
Reporter: Jenny Gee
1. Create a project
2. Don't add ANY platforms and run prepare:
ci003068684:Some Directory jgee$ cordova prepare firefoxos
cp: copyFileSync: could not write to dest file
(code=ENOENT):/Users/jgee/RippleSites/cordovaTest/Some
Directory/platforms/firefoxos/www/config.xml
{ [Error: ENOENT, no such file or directory
'/Users/jgee/RippleSites/cordovaTest/Some Directory/platforms/firefoxos']
errno: 34,
code: 'ENOENT',
path: '/Users/jgee/RippleSites/cordovaTest/Some
Directory/platforms/firefoxos',
syscall: 'readdir' }
If you run the BlackBerry one, you get a nicer message.
ci003068684:Some Directory jgee$ cordova prepare blackberry10
[Error: The provided path /Users/jgee/RippleSites/cordovaTest/Some
Directory/platforms/blackberry10 is not a Cordova BlackBerry10 project.]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-5141) FirefoxOS - fix version script permissions
[ https://issues.apache.org/jira/browse/CB-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zalewa resolved CB-5141. -- Resolution: Fixed FirefoxOS - fix version script permissions -- Key: CB-5141 URL: https://issues.apache.org/jira/browse/CB-5141 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Affects Versions: 3.1.0 Reporter: Josh Soref Assignee: Josh Soref Run this: cordova create test; cd test; cordova platform add firefoxos; cordova platform Actual results: Installed platforms: firefoxos Available platforms: android, blackberry10, ios Expected results: Installed platforms: firefoxos 3.1.0 Available platforms: android, blackberry10, ios -- This works on Android and iOS (and will work properly on BlackBerry 10 shortly) This is major because it was major for the other platforms... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5415) FxOS plugin permissions documentation
[ https://issues.apache.org/jira/browse/CB-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Zalewa resolved CB-5415. -- Resolution: Fixed All plugins which do need an app to have any permissions do have either documention with such information or are ready for 3.5 where plugins will change the manifest if needed automatically FxOS plugin permissions documentation - Key: CB-5415 URL: https://issues.apache.org/jira/browse/CB-5415 Project: Apache Cordova Issue Type: Task Components: FirefoxOS Affects Versions: 3.2.0 Reporter: Herm Wong Assignee: Herm Wong List of all permissions in FxOS. As plugins are completed the permissions required for the manifest.webapp should be documented with the corresponding API. https://developer.mozilla.org/en-US/Apps/Developing/App_permissions?redirectlocale=en-USredirectslug=Web%2FApps%2FApp_permissions -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6728) Support chip architecture as an option when building Windows and Windows Phone projects
Vladimir Kotikov created CB-6728:
Summary: Support chip architecture as an option when building
Windows and Windows Phone projects
Key: CB-6728
URL: https://issues.apache.org/jira/browse/CB-6728
Project: Apache Cordova
Issue Type: Improvement
Components: CLI, Windows 8, WP8
Affects Versions: 3.4.0
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
Currently apps for Windows 8 and Windows Phone 8 are targeted to AnyCPU
architecture, which is universal, but sometimes it's critical to build
application for specific processor architecture.
In our case WebSQL plugin contains C++ sources and use prepackage hook. And it
need to be built for specific architecture (x84, x64, ARM, not univeral AnyCPU)
It would be great if we can provide additional flag like `--x64`, or `--arm`
{noformat}
cordova build windows8 --release --x64
cordova build wp8 --arm
{noformat} to specify, how binaries should be built. Of course, if the flag is
not specified, `AnuCPU` target platform should be used by default.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6728) Support chip architecture as an option when building Windows and Windows Phone projects
[
https://issues.apache.org/jira/browse/CB-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-6728:
-
Description:
Currently apps for Windows 8 and Windows Phone 8 are targeted to AnyCPU
architecture, which is universal, but sometimes it's critical to build
application for specific processor architecture.
In our case WebSQL plugin contains C++ sources and use prepackage hook. And it
need to be built for specific architecture (x84, x64, ARM, not univeral AnyCPU)
It would be great if we can provide additional flag like `-x64`, `-x86` or
`-arm` {noformat}
cordova build windows8 --release --x64
cordova build wp8 --arm
{noformat} to specify, how binaries should be built. Of course, if the flag is
not specified, `AnuCPU` target platform should be used by default.
was:
Currently apps for Windows 8 and Windows Phone 8 are targeted to AnyCPU
architecture, which is universal, but sometimes it's critical to build
application for specific processor architecture.
In our case WebSQL plugin contains C++ sources and use prepackage hook. And it
need to be built for specific architecture (x84, x64, ARM, not univeral AnyCPU)
It would be great if we can provide additional flag like `--x64`, or `--arm`
{noformat}
cordova build windows8 --release --x64
cordova build wp8 --arm
{noformat} to specify, how binaries should be built. Of course, if the flag is
not specified, `AnuCPU` target platform should be used by default.
Support chip architecture as an option when building Windows and Windows
Phone projects
---
Key: CB-6728
URL: https://issues.apache.org/jira/browse/CB-6728
Project: Apache Cordova
Issue Type: Improvement
Components: CLI, Windows 8, WP8
Affects Versions: 3.4.0
Reporter: Vladimir Kotikov
Assignee: Jesse MacFadyen
Labels: arm, cli, windows, wp8, x64, x86
Currently apps for Windows 8 and Windows Phone 8 are targeted to AnyCPU
architecture, which is universal, but sometimes it's critical to build
application for specific processor architecture.
In our case WebSQL plugin contains C++ sources and use prepackage hook. And
it need to be built for specific architecture (x84, x64, ARM, not univeral
AnyCPU)
It would be great if we can provide additional flag like `-x64`, `-x86` or
`-arm` {noformat}
cordova build windows8 --release --x64
cordova build wp8 --arm
{noformat} to specify, how binaries should be built. Of course, if the flag
is not specified, `AnuCPU` target platform should be used by default.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004870#comment-14004870 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906514 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -64,8 +64,9 @@ whose assets you pull down to local working directories. To install the `cordova` command-line tool, follow these steps: 1. Download and install [Node.js](http://nodejs.org/). Following - installation, you should be able to invoke `node` or `npm` on your - command line. + installation, you should be able to invoke `node` and `npm` on your + command line. If desired, you may optionally use a tool such as `nvm` + or `nave` to manage your Node.js installation. --- End diff -- s/installation/installations/ ? clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004872#comment-14004872 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906580 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -73,22 +74,41 @@ To install the `cordova` command-line tool, follow these steps: the CLI does use it behind-the-scenes to download some assets when creating a new project. -1. Install the `cordova` utility. In Unix, prefixing the additional - `sudo` command may be necessary to install development utilities in - otherwise restricted directories: +1. Install the `cordova` module using Node.js' `npm` utility. The cordova --- End diff -- s/The cordova/The Cordova/ -- if you're using it as the brand (at the end as opposed to the module). s/The cordova/The `cordova`/ -- if you're using it in the same way as at the beginning of the line. I think the latter is what you want here. clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004876#comment-14004876 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906648 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -73,22 +74,41 @@ To install the `cordova` command-line tool, follow these steps: the CLI does use it behind-the-scenes to download some assets when creating a new project. -1. Install the `cordova` utility. In Unix, prefixing the additional - `sudo` command may be necessary to install development utilities in - otherwise restricted directories: +1. Install the `cordova` module using Node.js' `npm` utility. The cordova --- End diff -- s/Node.js'/`Node.js`'s/ Node.js is not a plural, nor is it **Greek** (*Moses*, *Jesus*), and therefore it is not eligible for possessive (`'`) without the `s` thus you need to use the pair (`'s`). clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004878#comment-14004878 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906677 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -73,22 +74,41 @@ To install the `cordova` command-line tool, follow these steps: the CLI does use it behind-the-scenes to download some assets when creating a new project. -1. Install the `cordova` utility. In Unix, prefixing the additional - `sudo` command may be necessary to install development utilities in - otherwise restricted directories: +1. Install the `cordova` module using Node.js' `npm` utility. The cordova + module will automatically be downloaded by the `npm` utility. -$ sudo npm install -g cordova + * on OS X and Linux: - The installation log may produce errors for any uninstalled - platform SDKs. Following installation, you should be able to run - `cordova` on the command line. +$ sudo npm install -g cordova + + On OS X and Linux, prefixing the `npm` command with + `sudo` may be necessary to install this development utility in + otherwise restricted directories such as + `/usr/local/share`. If you are using the optional + nvm/nave tool or have write access to the install directory, + you may be able to omit the `sudo` prefix. There are + [more tips](http://justjs.com/posts/npm-link-developing-your-own-npm-modules-without-tears) + available on using `npm` without `sudo`, if you desire to do that. + + * on Windows: + +C:\npm install -g cordova + + The `-g` flag above tells `npm` to install cordova globally. Otherwise --- End diff -- cordova = `cordova` or **Cordova** as appropriate (see earlier explanation) clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004881#comment-14004881 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906784 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -73,22 +74,41 @@ To install the `cordova` command-line tool, follow these steps: the CLI does use it behind-the-scenes to download some assets when creating a new project. -1. Install the `cordova` utility. In Unix, prefixing the additional - `sudo` command may be necessary to install development utilities in - otherwise restricted directories: +1. Install the `cordova` module using Node.js' `npm` utility. The cordova + module will automatically be downloaded by the `npm` utility. -$ sudo npm install -g cordova + * on OS X and Linux: --- End diff -- **OS X** and **Linux** here (and elsewhere) clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004883#comment-14004883 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on the pull request: https://github.com/apache/cordova-docs/pull/205#issuecomment-43782968 I like this (I don't usually spend time commenting on things I don't like...) clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6680) clarify instructions for installing via npm and sudo
[ https://issues.apache.org/jira/browse/CB-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004879#comment-14004879 ] ASF GitHub Bot commented on CB-6680: Github user jsoref commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/205#discussion_r12906738 --- Diff: docs/en/edge/guide/cli/index.md --- @@ -73,22 +74,41 @@ To install the `cordova` command-line tool, follow these steps: the CLI does use it behind-the-scenes to download some assets when creating a new project. -1. Install the `cordova` utility. In Unix, prefixing the additional - `sudo` command may be necessary to install development utilities in - otherwise restricted directories: +1. Install the `cordova` module using Node.js' `npm` utility. The cordova + module will automatically be downloaded by the `npm` utility. -$ sudo npm install -g cordova + * on OS X and Linux: - The installation log may produce errors for any uninstalled - platform SDKs. Following installation, you should be able to run - `cordova` on the command line. +$ sudo npm install -g cordova + + On OS X and Linux, prefixing the `npm` command with + `sudo` may be necessary to install this development utility in + otherwise restricted directories such as + `/usr/local/share`. If you are using the optional + nvm/nave tool or have write access to the install directory, + you may be able to omit the `sudo` prefix. There are + [more tips](http://justjs.com/posts/npm-link-developing-your-own-npm-modules-without-tears) + available on using `npm` without `sudo`, if you desire to do that. + + * on Windows: + +C:\npm install -g cordova + + The `-g` flag above tells `npm` to install cordova globally. Otherwise + it will be installed in a subdirectory of the current working directory. --- End diff -- Add (`c:\` in this example). I'd suggest `pushd %USERPROFILE%` before the npm install example to suggest a reasonable directory. Also clarify that *subdirectory* means `node_modules\cordova` clarify instructions for installing via npm and sudo Key: CB-6680 URL: https://issues.apache.org/jira/browse/CB-6680 Project: Apache Cordova Issue Type: Improvement Components: Docs Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor The Linux person inside me says that using sudo to install and run things ought to be avoided if possible. http://markmail.org/thread/bfj4lywpbzn6mtdr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5650) make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004946#comment-14004946 ] Shazron Abdullah commented on CB-5650: -- +1 to Marcel's string suggestion make visible the version of the Cordova native lib -- Key: CB-5650 URL: https://issues.apache.org/jira/browse/CB-5650 Project: Apache Cordova Issue Type: Improvement Components: Android, BlackBerry, iOS, Ubuntu, WP8 Reporter: Marcel Kinard Assignee: Martin Gonzalez Priority: Minor We recently had a situation where a consumer had mismatched the runtime: one version of cordova.js and another version of the Cordova native code. The consumer gave us their compiled app, so we didn't have access to the native's source in the project. We had an idea that it would be nice if the native code compiled in some marker so we could tell what version it was without the source. Perhaps issue a log on startup saying Greetings from Cordova native code 3.2.0, or have something compiled in that would appear in strings cordova.jar | grep version. See some discussion at http://markmail.org/thread/m4h4csvcq4cs3dcr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5751) FirefoxOS build issue
[ https://issues.apache.org/jira/browse/CB-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Soref updated CB-5751: --- Assignee: Gert-Jan Braas FirefoxOS build issue - Key: CB-5751 URL: https://issues.apache.org/jira/browse/CB-5751 Project: Apache Cordova Issue Type: Bug Components: CLI, FirefoxOS Affects Versions: 3.3.0 Environment: Windows 7 amd64 Cordova 3.3.1-0.1.2 nodejs v0.10.24 Reporter: Vincenzo Assignee: Gert-Jan Braas Fix For: 3.5.0 After typing cordova platform add firefoxos and cordova build I read this error: C:\Users\Utente\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126 throw e; ^ Error: An error occurred while building the firefoxos project.c:\Linkpass\platf orms\firefoxos\cordova\build non ´┐¢ riconosciuto come comando interno o estern o, un programma eseguibile o un file batch. at ChildProcess.anonymous (C:\Users\Utente\AppData\Roaming\npm\node_module s\cordova\src\compile.js:65:22) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:735:16) at Socket.anonymous (child_process.js:948:11) at Socket.EventEmitter.emit (events.js:95:17) at Pipe.close (net.js:466:12) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5651) [iOS] make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-5651. -- Resolution: Fixed Assignee: Shazron Abdullah [iOS] make visible the version of the Cordova native lib Key: CB-5651 URL: https://issues.apache.org/jira/browse/CB-5651 Project: Apache Cordova Issue Type: Sub-task Components: iOS Reporter: Marcel Kinard Assignee: Shazron Abdullah Priority: Minor See parent task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5651) [iOS] make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004969#comment-14004969 ] ASF subversion and git services commented on CB-5651: - Commit c820888a32af7d46c6aeb28f66eba391157643b6 in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=c820888 ] CB-5651 - [iOS] make visible the version of the Cordova native lib [iOS] make visible the version of the Cordova native lib Key: CB-5651 URL: https://issues.apache.org/jira/browse/CB-5651 Project: Apache Cordova Issue Type: Sub-task Components: iOS Reporter: Marcel Kinard Priority: Minor See parent task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6729) Update printDeprecationNotice to new name, and new warning for iOS 6.0
Shazron Abdullah created CB-6729: Summary: Update printDeprecationNotice to new name, and new warning for iOS 6.0 Key: CB-6729 URL: https://issues.apache.org/jira/browse/CB-6729 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah in CDVVIewController.m The existing warning is obsolete. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6729) Update printDeprecationNotice to new name, and new warning for iOS 6.0
[ https://issues.apache.org/jira/browse/CB-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004973#comment-14004973 ] ASF subversion and git services commented on CB-6729: - Commit 945a352eb658b278de1c3b8ca2cd548789940cf0 in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=945a352 ] CB-6729 - Update printDeprecationNotice to new name, and new warning for iOS 6.0 Update printDeprecationNotice to new name, and new warning for iOS 6.0 Key: CB-6729 URL: https://issues.apache.org/jira/browse/CB-6729 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah in CDVVIewController.m The existing warning is obsolete. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6729) Update printDeprecationNotice to new name, and new warning for iOS 6.0
[ https://issues.apache.org/jira/browse/CB-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-6729. -- Resolution: Fixed Update printDeprecationNotice to new name, and new warning for iOS 6.0 Key: CB-6729 URL: https://issues.apache.org/jira/browse/CB-6729 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah in CDVVIewController.m The existing warning is obsolete. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6730) Image file names containing @2x are always blocked by the whitelist on blackberry10 platform
Rowell Cruz created CB-6730: --- Summary: Image file names containing @2x are always blocked by the whitelist on blackberry10 platform Key: CB-6730 URL: https://issues.apache.org/jira/browse/CB-6730 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.4.0 Reporter: Rowell Cruz Image file names containing @2x will be blocked by the whitelist even if the domain if correctly whitelisted. This issue occurs on blackberry10 platform. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005115#comment-14005115 ] Jesse MacFadyen commented on CB-6721: - The reason the tests are failing on iOS is that every time we stop and start listening to battery level changes, the native code sets 'level' to 'null'. In my mind, the native code should hang on to the last value it received, so that 'null' is only ever sent the first time the native code 'start' is called. This can be fixed purely in javascript by ignoring status changes we receive where our previous value was non-null. Some interesting edge cases are revealed by this, although I do not want to spend too much time on a deprecated spec... What is the expected result of a change from : null = LOW null = CRITICAL Presumably, if we choose to fire the events then every time a user starts the app while the battery is less than LOW it will fire. iOS Failed test: battery.spec.4 should fire batterycritical events -- Key: CB-6721 URL: https://issues.apache.org/jira/browse/CB-6721 Project: Apache Cordova Issue Type: Bug Components: mobile-spec, Plugin Battery Status Reporter: Shazron Abdullah Assignee: Jesse MacFadyen Battery (navigator.battery) battery.spec.4 should fire batterycritical events. timeout: timed out after 100 msec waiting for batterycritical onEvent was not called when level goes from 19-5 This test is new for CB-4520 CB-4519: https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005136#comment-14005136 ] ASF subversion and git services commented on CB-6721: - Commit b48708e7f733fc5612559120d2f0587b70ad0a82 in cordova-plugin-battery-status's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-battery-status.git;h=b48708e ] CB-6721 ignore null values if previous value was not null iOS Failed test: battery.spec.4 should fire batterycritical events -- Key: CB-6721 URL: https://issues.apache.org/jira/browse/CB-6721 Project: Apache Cordova Issue Type: Bug Components: mobile-spec, Plugin Battery Status Reporter: Shazron Abdullah Assignee: Jesse MacFadyen Battery (navigator.battery) battery.spec.4 should fire batterycritical events. timeout: timed out after 100 msec waiting for batterycritical onEvent was not called when level goes from 19-5 This test is new for CB-4520 CB-4519: https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6731) Geolocation constants not defined in Android
Michael Hoisie created CB-6731: -- Summary: Geolocation constants not defined in Android Key: CB-6731 URL: https://issues.apache.org/jira/browse/CB-6731 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.4.0 Environment: Nexus 5 / Cordova 3.4.1-0.1.0 Reporter: Michael Hoisie Priority: Minor The geolocation constants are not defined in Android: PositionError.PERMISSION_DENIED PositionError.POSITION_UNAVAILABLE PositionError.TIMEOUT They are documented here: http://plugins.cordova.io/#/package/org.apache.cordova.geolocation Not sure if this is a documentation bug. These constants exist in iOS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6732) [WP8] Fix MSBuild 64 bit is not supported build error
Sergey Grebnov created CB-6732: -- Summary: [WP8] Fix MSBuild 64 bit is not supported build error Key: CB-6732 URL: https://issues.apache.org/jira/browse/CB-6732 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 3.5.0 Environment: Windows 8.x x64, VS 2013 Reporter: Sergey Grebnov Assignee: Sergey Grebnov From dev mail thread: Our change to not require msbuild in the user environment path is failing. System returns (respectively) : C:\Program Files (x86)\MSBuild\12.0\bin\amd64\ and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ Which results in the following error message: Building Windows Phone application using MSBuild 64 bit is not supported. If you are using TFS build definitions, change the MSBuild platform to x86. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6732) [WP8] Fix MSBuild 64 bit is not supported build error
[ https://issues.apache.org/jira/browse/CB-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005606#comment-14005606 ] Sergey Grebnov commented on CB-6732: From Stefan The problem comes from the bitness of the process you are executing the command from. I guess that you have 64bit Node.js installation and that's why `cordova build wp8` does not works for you, but calling directly the platform script works. It all boils down to the registry key setting for MSBuildToolsPath which is: - for 64-bit process ( *HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0*) - C:\Program Files (x86)\MSBuild\12.0\bin\amd64\ - and shimmed for 32bit process on 64bit architectures ( *HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSBuild\ToolsVersions\12.0*) - C:\Program Files (x86)\MSBuild\12.0\bin\ I have VS 2013 Update 2 on my machine. I do not have any other VS installations. [WP8] Fix MSBuild 64 bit is not supported build error --- Key: CB-6732 URL: https://issues.apache.org/jira/browse/CB-6732 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 3.5.0 Environment: Windows 8.x x64, VS 2013 Reporter: Sergey Grebnov Assignee: Sergey Grebnov From dev mail thread: Our change to not require msbuild in the user environment path is failing. System returns (respectively) : C:\Program Files (x86)\MSBuild\12.0\bin\amd64\ and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ Which results in the following error message: Building Windows Phone application using MSBuild 64 bit is not supported. If you are using TFS build definitions, change the MSBuild platform to x86. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6732) [WP8] Fix MSBuild 64 bit is not supported build error
[ https://issues.apache.org/jira/browse/CB-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005621#comment-14005621 ] Sergey Grebnov commented on CB-6732: Possible approaches: 1. Use regexp to remove amd64 at the end. MSBuild folders structure is strongly defined so the risk that there is no x86 msbuild version uneder /bin folder is low. 2. Adding Wow6432Node when running in x64 mode. 3. Running %VS120COMNTOOLS%\vsvars32.bat before build to provision required environment, after that we can use 'msbuild' and we don't need to manually search for location 4. Use (/p:PlatformTarget=x86) as per http://stackoverflow.com/a/17461224/255654. Does not work. [WP8] Fix MSBuild 64 bit is not supported build error --- Key: CB-6732 URL: https://issues.apache.org/jira/browse/CB-6732 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 3.5.0 Environment: Windows 8.x x64, VS 2013 Reporter: Sergey Grebnov Assignee: Sergey Grebnov From dev mail thread: Our change to not require msbuild in the user environment path is failing. System returns (respectively) : C:\Program Files (x86)\MSBuild\12.0\bin\amd64\ and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ Which results in the following error message: Building Windows Phone application using MSBuild 64 bit is not supported. If you are using TFS build definitions, change the MSBuild platform to x86. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-6732) [WP8] Fix MSBuild 64 bit is not supported build error
[ https://issues.apache.org/jira/browse/CB-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005621#comment-14005621 ] Sergey Grebnov edited comment on CB-6732 at 5/22/14 5:21 AM: - Possible approaches: 1. Use regexp to remove amd64 at the end. MSBuild folders structure is strongly defined so the risk that there is no x86 msbuild version uneder /bin folder is low. 2. Adding Wow6432Node when running in x64 mode - use ProcEnv(PROCESSOR_ARCHITECTURE) = AMD64 3. Running %VS120COMNTOOLS%\vsvars32.bat before build to provision required environment, after that we can use 'msbuild' and we don't need to manually search for location 4. Use (/p:PlatformTarget=x86) as per http://stackoverflow.com/a/17461224/255654. Does not work. 5. Try to create/set x32 mode for WScript.Shell was (Author: sgrebnov): Possible approaches: 1. Use regexp to remove amd64 at the end. MSBuild folders structure is strongly defined so the risk that there is no x86 msbuild version uneder /bin folder is low. 2. Adding Wow6432Node when running in x64 mode. 3. Running %VS120COMNTOOLS%\vsvars32.bat before build to provision required environment, after that we can use 'msbuild' and we don't need to manually search for location 4. Use (/p:PlatformTarget=x86) as per http://stackoverflow.com/a/17461224/255654. Does not work. [WP8] Fix MSBuild 64 bit is not supported build error --- Key: CB-6732 URL: https://issues.apache.org/jira/browse/CB-6732 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 3.5.0 Environment: Windows 8.x x64, VS 2013 Reporter: Sergey Grebnov Assignee: Sergey Grebnov From dev mail thread: Our change to not require msbuild in the user environment path is failing. System returns (respectively) : C:\Program Files (x86)\MSBuild\12.0\bin\amd64\ and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ Which results in the following error message: Building Windows Phone application using MSBuild 64 bit is not supported. If you are using TFS build definitions, change the MSBuild platform to x86. -- This message was sent by Atlassian JIRA (v6.2#6252)
