[jira] [Assigned] (CB-8283) Auto-add missing platforms when needed (i.e. `cordova run android` should add android)
[ https://issues.apache.org/jira/browse/CB-8283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks reassigned CB-8283: -- Assignee: Michael Brooks Auto-add missing platforms when needed (i.e. `cordova run android` should add android) -- Key: CB-8283 URL: https://issues.apache.org/jira/browse/CB-8283 Project: Apache Cordova Issue Type: New Feature Components: CLI, CordovaLib Reporter: Michal Mocny Assignee: Michael Brooks Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-7889) Add noindex meta tag to old releases
Michael Brooks created CB-7889: -- Summary: Add noindex meta tag to old releases Key: CB-7889 URL: https://issues.apache.org/jira/browse/CB-7889 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 4.0.0 Reporter: Michael Brooks Assignee: Michael Brooks Fix For: 4.0.0 Search results often turn up old versions of the documentation. In order to prevent this, we can use the noindex meta tag on outdated versions of the documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7889) Add noindex meta tag to old releases
[
https://issues.apache.org/jira/browse/CB-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14187437#comment-14187437
]
Michael Brooks commented on CB-7889:
The above commit will have the following logic:
*When 4.0.0 is the latest release:*
- All English 4.0.0 documentation will be indexed by a search engine
- All other documentation will ignored
*When 4.1.0 becomes the latest release:*
- All English 4.1.0 will be indexed
- All other documentation will be ignored (including 4.0.0)
I used the following tag to prevent indexing:
{noformat}
meta name=robots content=noindex
{noformat}
Let me know if there are any issues with this approach!
Add noindex meta tag to old releases
Key: CB-7889
URL: https://issues.apache.org/jira/browse/CB-7889
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 4.0.0
Reporter: Michael Brooks
Assignee: Michael Brooks
Fix For: 4.0.0
Search results often turn up old versions of the documentation.
In order to prevent this, we can use the noindex meta tag on outdated
versions of the documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-7889) Add noindex meta tag to old releases
[ https://issues.apache.org/jira/browse/CB-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks closed CB-7889. -- Resolution: Fixed Add noindex meta tag to old releases Key: CB-7889 URL: https://issues.apache.org/jira/browse/CB-7889 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 4.0.0 Reporter: Michael Brooks Assignee: Michael Brooks Fix For: 4.0.0 Search results often turn up old versions of the documentation. In order to prevent this, we can use the noindex meta tag on outdated versions of the documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152506#comment-14152506
]
Michael Brooks edited comment on CB-7665 at 9/30/14 4:12 PM:
-
Hi [~websteve],
I thought I'd chime-in on how I've done Android releases in the past using the
{{--release}} flag. It's not exactly straight-forward, because Cordova has not
yet created a unified way to define signing keys to build a release.
First off, I'd recommending reading through the [Preparing for a
Release|http://developer.android.com/tools/publishing/preparing.html] guides on
Android's Developer page. The most important section is _Building with Ant_
near the bottom of the page.
The release flag essentially calls the {{ant release}} task. So, by setting up
the Android project to build signed releases with {{ant release}}, then the
{{--release}} flag will also build signed releases. The [Building in Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#ReleaseMode]
guide will explain how to setup your project to automatically sign and align
your application using your specified keystore and alias.
Personally, I don't like to store my signing keys in my project. In open source
applications, such as the _PhoneGap Developer App_, I [reference the keys in an
external
directory|https://github.com/phonegap/phonegap-app-developer/blob/master/platforms/android/project.properties#L21-L22].
Your team can then share the signing key directory however you want.
was (Author: mwbrooks):
Hi [~shuston],
I thought I'd chime-in on how I've done Android releases in the past using the
{{--release}} flag. It's not exactly straight-forward, because Cordova has not
yet created a unified way to define signing keys to build a release.
First off, I'd recommending reading through the [Preparing for a
Release|http://developer.android.com/tools/publishing/preparing.html] guides on
Android's Developer page. The most important section is _Building with Ant_
near the bottom of the page.
The release flag essentially calls the {{ant release}} task. So, by setting up
the Android project to build signed releases with {{ant release}}, then the
{{--release}} flag will also build signed releases. The [Building in Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#ReleaseMode]
guide will explain how to setup your project to automatically sign and align
your application using your specified keystore and alias.
Personally, I don't like to store my signing keys in my project. In open source
applications, such as the _PhoneGap Developer App_, I [reference the keys in an
external
directory|https://github.com/phonegap/phonegap-app-developer/blob/master/platforms/android/project.properties#L21-L22].
Your team can then share the signing key directory however you want.
Release process for Google Play has no documentation, requires guesswork!
--
Key: CB-7665
URL: https://issues.apache.org/jira/browse/CB-7665
Project: Apache Cordova
Issue Type: Improvement
Components: Android, CLI, Docs
Affects Versions: 3.5.0
Environment: Mac OS X Lion
Reporter: Steve Husting
Labels: patch
Fix For: 3.5.0
I output my myApp version 12 project with: cordova build android --release
It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk
I changed the name to the final apk name: myApp-release-unsigned.apk =
myApp.apk
I copied the myApp.keystore file used on earlier myApps to the same folder.
Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA
-digestalg SHA1 -keystore myApp.keystore myApp.apk myApp
I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk
When I uploaded the myApp.apk to Google Play, it said that the file needed to
be zipaligned.
The verbose output shows zipalign being done. So is there a bug when the apk
is made via cordova build android --release?
Is there a step missing that I should be taking? Unfortunately, all the
instructions for this on the Internet assume I'm not using Cordova.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153330#comment-14153330
]
Michael Brooks commented on CB-7665:
Hi [~websteve],
You're right, that would be hard to believe! But no, that's not what I'm trying
to say.
When you run {{cordova build android}}, the Cordova CLI will prepare and build
the Android project.
In the prepare step, it will translate the Cordova directory structure to the
Android project. It merges web assets from {{merges/}} into {{www/}}, copies
the {{www/}} assets into the Android project {{platforms/android}}, and runs
some transforms described in {{config.xml}} against the Android project.
In the build step, it would execute {{ant debug}} in the Android project
{{platforms/android}}. I believe {{ant debug}} in turn calls {{ant build}}.
This will produce an unsigned APK.
When you run {{cordova build android --release}}, the prepare step is identical
but the build step will instead execute {{ant release}}. The Android
documentation on [Building in Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#ReleaseMode]
explains that {{ant release}} will automatically sign and align your
application using a specified keystore and alias. So, if you setup the keystore
and alias correctly, {{cordova build android --release}} will produce a signed
APK.
I hope that makes more sense!
Michael
Release process for Google Play has no documentation, requires guesswork!
--
Key: CB-7665
URL: https://issues.apache.org/jira/browse/CB-7665
Project: Apache Cordova
Issue Type: Improvement
Components: Android, CLI, Docs
Affects Versions: 3.5.0
Environment: Mac OS X Lion
Reporter: Steve Husting
Labels: patch
Fix For: 3.5.0
I output my myApp version 12 project with: cordova build android --release
It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk
I changed the name to the final apk name: myApp-release-unsigned.apk =
myApp.apk
I copied the myApp.keystore file used on earlier myApps to the same folder.
Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA
-digestalg SHA1 -keystore myApp.keystore myApp.apk myApp
I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk
When I uploaded the myApp.apk to Google Play, it said that the file needed to
be zipaligned.
The verbose output shows zipalign being done. So is there a bug when the apk
is made via cordova build android --release?
Is there a step missing that I should be taking? Unfortunately, all the
instructions for this on the Internet assume I'm not using Cordova.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153360#comment-14153360
]
Michael Brooks commented on CB-7665:
Hi [~websteve],
I'm by no means an expert at Android development and I was hoping that some of
my (stumbled by) success would help you as well!
I think it's suspicious that running {{cordova build android --release}} only
generates:
{noformat}
/myApp/platforms/android/ant-build/myApp-release-unsigned.apk
{noformat}
When I run the same comment, it will also generate:
{noformat}
/myApp/platforms/android/ant-build/myApp-release.apk
{noformat}
Have you updated {{platforms/android/project.properties}} with your keystore
information? In the Android [Auto Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#AutoReleaseMode]
documentation, they explain that you must specify the keystore and alias. When
this is done correctly, you will be prompted for your keystore password after
running {{cordova build android --release}}.
{noformat}
# file: /myApp/platforms/android/project.properties
# your path and alias may be different from this
key.store=../../../path/to/your/myApp.keystore
key.alias=myApp
{noformat}
You can also test with the Android tooling by running:
{noformat}
$ cd myApp/platforms/android
$ ant release
{noformat}
[~bowserj] is correct that Cordova does not yet support release steps. Some
platforms have implemented the {{--release}} flag, but there is no consistent
way to do it on all of the platforms. Eventually that'll happen. However,
because the Android {{--release}} flag uses {{ant release}} under the hood, we
can get release builds happening with just a little bit of work.
Release process for Google Play has no documentation, requires guesswork!
--
Key: CB-7665
URL: https://issues.apache.org/jira/browse/CB-7665
Project: Apache Cordova
Issue Type: Improvement
Components: Android, CLI, Docs
Affects Versions: 3.5.0
Environment: Mac OS X Lion
Reporter: Steve Husting
Labels: patch
Fix For: 3.5.0
I output my myApp version 12 project with: cordova build android --release
It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk
I changed the name to the final apk name: myApp-release-unsigned.apk =
myApp.apk
I copied the myApp.keystore file used on earlier myApps to the same folder.
Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA
-digestalg SHA1 -keystore myApp.keystore myApp.apk myApp
I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk
When I uploaded the myApp.apk to Google Play, it said that the file needed to
be zipaligned.
The verbose output shows zipalign being done. So is there a bug when the apk
is made via cordova build android --release?
Is there a step missing that I should be taking? Unfortunately, all the
instructions for this on the Internet assume I'm not using Cordova.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CB-7665) Release process for Google Play has no documentation, requires guesswork!
[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153360#comment-14153360
]
Michael Brooks edited comment on CB-7665 at 9/30/14 4:34 PM:
-
Hi [~websteve],
I'm by no means an expert at Android development and I was hoping that some of
my (stumbled by) success would help you as well!
I think it's suspicious that running {{cordova build android --release}} only
generates:
{noformat}
/myApp/platforms/android/ant-build/myApp-release-unsigned.apk
{noformat}
When I run the same command, it will also generate:
{noformat}
/myApp/platforms/android/ant-build/myApp-release.apk
{noformat}
Have you updated {{platforms/android/project.properties}} with your keystore
information? In the Android [Auto Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#AutoReleaseMode]
documentation, they explain that you must specify the keystore and alias. When
this is done correctly, you will be prompted for your keystore password after
running {{cordova build android --release}}.
{noformat}
# file: /myApp/platforms/android/project.properties
# your path and alias may be different from this
key.store=../../../path/to/your/myApp.keystore
key.alias=myApp
{noformat}
You can also test with the Android tooling by running:
{noformat}
$ cd myApp/platforms/android
$ ant release
{noformat}
[~bowserj] is correct that Cordova does not yet support release steps. Some
platforms have implemented the {{--release}} flag, but there is no consistent
way to do it on all of the platforms. Eventually that'll happen. However,
because the Android {{--release}} flag uses {{ant release}} under the hood, we
can get release builds happening with just a little bit of work.
was (Author: mwbrooks):
Hi [~websteve],
I'm by no means an expert at Android development and I was hoping that some of
my (stumbled by) success would help you as well!
I think it's suspicious that running {{cordova build android --release}} only
generates:
{noformat}
/myApp/platforms/android/ant-build/myApp-release-unsigned.apk
{noformat}
When I run the same comment, it will also generate:
{noformat}
/myApp/platforms/android/ant-build/myApp-release.apk
{noformat}
Have you updated {{platforms/android/project.properties}} with your keystore
information? In the Android [Auto Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#AutoReleaseMode]
documentation, they explain that you must specify the keystore and alias. When
this is done correctly, you will be prompted for your keystore password after
running {{cordova build android --release}}.
{noformat}
# file: /myApp/platforms/android/project.properties
# your path and alias may be different from this
key.store=../../../path/to/your/myApp.keystore
key.alias=myApp
{noformat}
You can also test with the Android tooling by running:
{noformat}
$ cd myApp/platforms/android
$ ant release
{noformat}
[~bowserj] is correct that Cordova does not yet support release steps. Some
platforms have implemented the {{--release}} flag, but there is no consistent
way to do it on all of the platforms. Eventually that'll happen. However,
because the Android {{--release}} flag uses {{ant release}} under the hood, we
can get release builds happening with just a little bit of work.
Release process for Google Play has no documentation, requires guesswork!
--
Key: CB-7665
URL: https://issues.apache.org/jira/browse/CB-7665
Project: Apache Cordova
Issue Type: Improvement
Components: Android, CLI, Docs
Affects Versions: 3.5.0
Environment: Mac OS X Lion
Reporter: Steve Husting
Labels: patch
Fix For: 3.5.0
I output my myApp version 12 project with: cordova build android --release
It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk
I changed the name to the final apk name: myApp-release-unsigned.apk =
myApp.apk
I copied the myApp.keystore file used on earlier myApps to the same folder.
Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA
-digestalg SHA1 -keystore myApp.keystore myApp.apk myApp
I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk
When I uploaded the myApp.apk to Google Play, it said that the file needed to
be zipaligned.
The verbose output shows zipalign being done. So is there a bug when the apk
is made via cordova build android --release?
Is there a step missing that I should be taking? Unfortunately, all the
instructions for this on the Internet assume I'm not using Cordova.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7665) Google Play does not detect zipalign in corova build android --release apk
[
https://issues.apache.org/jira/browse/CB-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152506#comment-14152506
]
Michael Brooks commented on CB-7665:
Hi [~shuston],
I thought I'd chime-in on how I've done Android releases in the past using the
{{--release}} flag. It's not exactly straight-forward, because Cordova has not
yet created a unified way to define signing keys to build a release.
First off, I'd recommending reading through the [Preparing for a
Release|http://developer.android.com/tools/publishing/preparing.html] guides on
Android's Developer page. The most important section is _Building with Ant_
near the bottom of the page.
The release flag essentially calls the {{ant release}} task. So, by setting up
the Android project to build signed releases with {{ant release}}, then the
{{--release}} flag will also build signed releases. The [Building in Release
Mode|http://developer.android.com/tools/building/building-cmdline.html#ReleaseMode]
guide will explain how to setup your project to automatically sign and align
your application using your specified keystore and alias.
Personally, I don't like to store my signing keys in my project. In open source
applications, such as the _PhoneGap Developer App_, I [reference the keys in an
external
directory|https://github.com/phonegap/phonegap-app-developer/blob/master/platforms/android/project.properties#L21-L22].
Your team can then share the signing key directory however you want.
Google Play does not detect zipalign in corova build android --release apk
--
Key: CB-7665
URL: https://issues.apache.org/jira/browse/CB-7665
Project: Apache Cordova
Issue Type: Improvement
Components: Android, CLI
Affects Versions: 3.5.0
Environment: Mac OS X Lion
Reporter: Steve Husting
Labels: patch
Fix For: 3.5.0
I output my myApp version 12 project with: cordova build android --release
It was output as myApp/platforms/android/ant-build/myApp-release-unsigned.apk
I changed the name to the final apk name: myApp-release-unsigned.apk =
myApp.apk
I copied the myApp.keystore file used on earlier myApps to the same folder.
Starting with that folder, I ran: jarsigner -verbose -sigalg SHA1withRSA
-digestalg SHA1 -keystore myApp.keystore myApp.apk myApp
I successfully verified it with: jarsigner -verify -verbose -certs myApp.apk
When I uploaded the myApp.apk to Google Play, it said that the file needed to
be zipaligned.
The verbose output shows zipalign being done. So is there a bug when the apk
is made via cordova build android --release?
Is there a step missing that I should be taking? Unfortunately, all the
instructions for this on the Internet assume I'm not using Cordova.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7407) [Release + 3.6.0] Change default docs to new version
[ https://issues.apache.org/jira/browse/CB-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14143719#comment-14143719 ] Michael Brooks commented on CB-7407: Updated the redirect to 3.6.0. [~cmarcelk] the Heroku server is setup to be accessed by anyone. Please sign up and Shaz, Andrew, or I can set you up with access as well. The README.md has complete details on the process involved. [~agrieve] I noticed that you updated the server to 3.5.0 (Thanks!) but you didn't push the commit to the cordova-labs repository. In the future, can you please remember to share the commits, otherwise it's confusing for people to diagnose why the Heroku and Apache remotes are out of sync. [Release + 3.6.0] Change default docs to new version Key: CB-7407 URL: https://issues.apache.org/jira/browse/CB-7407 Project: Apache Cordova Issue Type: Sub-task Components: Amazon FireOS, Android, App Hello World, BlackBerry, CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 Reporter: Steve Gill Assignee: Michael Brooks Fix For: 3.6.0 Refer to Workflow here: http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CB-7407) [Release + 3.6.0] Change default docs to new version
[ https://issues.apache.org/jira/browse/CB-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks closed CB-7407. -- Resolution: Fixed [Release + 3.6.0] Change default docs to new version Key: CB-7407 URL: https://issues.apache.org/jira/browse/CB-7407 Project: Apache Cordova Issue Type: Sub-task Components: Amazon FireOS, Android, App Hello World, BlackBerry, CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 Reporter: Steve Gill Assignee: Michael Brooks Fix For: 3.6.0 Refer to Workflow here: http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7564) Renaming project can incorrectly rename files.
Michael Brooks created CB-7564:
--
Summary: Renaming project can incorrectly rename files.
Key: CB-7564
URL: https://issues.apache.org/jira/browse/CB-7564
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 3.5.0
Reporter: Michael Brooks
Priority: Minor
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error. This
is because Xcode file references for Data_Foo.m and Data_Foo.h are updated
to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example.
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
A real-life example can be found in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-7564) Renaming project can incorrectly rename files.
[
https://issues.apache.org/jira/browse/CB-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks updated CB-7564:
---
Description:
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error. This
is because Xcode file references for Data_Foo.m and Data_Foo.h are updated
to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example:
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
was:
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error. This
is because Xcode file references for Data_Foo.m and Data_Foo.h are updated
to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example.
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
Renaming project can incorrectly rename files.
--
Key: CB-7564
URL: https://issues.apache.org/jira/browse/CB-7564
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 3.5.0
Reporter: Michael Brooks
Priority: Minor
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error.
This is because Xcode file references for Data_Foo.m and Data_Foo.h are
updated to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example:
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-7564) Renaming project can incorrectly rename files.
[
https://issues.apache.org/jira/browse/CB-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks updated CB-7564:
---
Description:
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error. This
is because Xcode file references for Data_Foo.m and Data_Foo.h are updated
to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example.
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
was:
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error. This
is because Xcode file references for Data_Foo.m and Data_Foo.h are updated
to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example.
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
A real-life example can be found in
Renaming project can incorrectly rename files.
--
Key: CB-7564
URL: https://issues.apache.org/jira/browse/CB-7564
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 3.5.0
Reporter: Michael Brooks
Priority: Minor
Consider a project with the name Foo in config.xml. This project also has a
plugin with the files Data_Foo.m and Data_Foo.h. When the project name is
changed from Foo to Bar and recompiled, it will produce a build error.
This is because Xcode file references for Data_Foo.m and Data_Foo.h are
updated to Data_Bar.m and Data_Bar.h.
---
You can reproduce this issue with a real-world example.
{noformat}
$ git clone https://github.com/phonegap/phonegap-app-developer.git
$ cd phonegap-app-developer/
$ cordova build ios
# should be successful
#
# edit www/config.xml
#update nameWhatever/name
#
$ cordova build ios
# should see a ADBMobile_Whatever.h error
#
# open the Xcode project and rename:
#Plugins/ADBMobile_Whatever.h = Plugins/ADBMobile_PhoneGap.h
#Plugins/ADBMobile_Whatever.m = Plugins/ADBMobile_PhoneGap.m
#
$ cordova build ios
# should be successful
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CB-7289) Broken plugin links on Platform Guide page
Michael Brooks created CB-7289: -- Summary: Broken plugin links on Platform Guide page Key: CB-7289 URL: https://issues.apache.org/jira/browse/CB-7289 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.5.0, Master Environment: http://cordova.apache.org/docs/en/3.5.0/guide_support_index.md.html Reporter: Michael Brooks Assignee: Michael Brooks The links point to the dev branch rather than the master branach. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-7289) Broken plugin links on Platform Guide page
[ https://issues.apache.org/jira/browse/CB-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-7289. Resolution: Fixed Broken plugin links on Platform Guide page -- Key: CB-7289 URL: https://issues.apache.org/jira/browse/CB-7289 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: Master, 3.5.0 Environment: http://cordova.apache.org/docs/en/3.5.0/guide_support_index.md.html Reporter: Michael Brooks Assignee: Michael Brooks The links point to the dev branch rather than the master branach. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5226) Write BlackBerry 10 Configuration
[ https://issues.apache.org/jira/browse/CB-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045331#comment-14045331 ] Michael Brooks commented on CB-5226: It's missing because the title is BlackBerry 10 Configuration not BlackBerry Configuration. https://raw.githubusercontent.com/apache/cordova-docs/master/docs/en/3.5.0/guide/platforms/blackberry10/config.md I can make the corrections in a few moments. Write BlackBerry 10 Configuration - Key: CB-5226 URL: https://issues.apache.org/jira/browse/CB-5226 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.1.0 Reporter: Josh Soref Priority: Minor Fix For: 3.3.0 http://cordova.apache.org/docs/en/3.1.0/guide_platforms_index.md.html#Platform%20Guides BlackBerry 10 BlackBerry 10 Platform Guide BlackBerry 10 Configuration - this is not a link/page BlackBerry 10 Plugins BlackBerry 10 Command-line Tools -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6676) WP Platform Scripts Support Unknown Flags
[
https://issues.apache.org/jira/browse/CB-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997985#comment-13997985
]
Michael Brooks commented on CB-6676:
Awesome, thank you Jesse!
WP Platform Scripts Support Unknown Flags
-
Key: CB-6676
URL: https://issues.apache.org/jira/browse/CB-6676
Project: Apache Cordova
Issue Type: Bug
Components: WP7, WP8
Affects Versions: 3.4.0
Reporter: Michael Brooks
Assignee: Jesse MacFadyen
Priority: Minor
Fix For: 3.6.0
*Expected Result*
A platform script should silently ignore unknown flags (parameters).
For example, {{--custom-flag}}
The reason is that Cordova CLI hooks can be used to enable custom flags.
*Current Result*
On WP, unknown flags [cause the script to exit with an error
code|https://github.com/apache/cordova-wp8/blob/master/wp8/template/cordova/lib/deploy.js#L324-L326].
On Android and iOS,the expected behaviour is matched.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6676) WP Platform Scripts Support Unknown Flags
Michael Brooks created CB-6676:
--
Summary: WP Platform Scripts Support Unknown Flags
Key: CB-6676
URL: https://issues.apache.org/jira/browse/CB-6676
Project: Apache Cordova
Issue Type: Bug
Components: WP7, WP8
Affects Versions: 3.4.0
Reporter: Michael Brooks
Assignee: Jesse MacFadyen
Priority: Minor
*Expected Result*
A platform script should silently ignore unknown flags (parameters).
For example, {{--custom-flag}}
The reason is that Cordova CLI hooks can be used to enable custom flags.
*Current Result*
On WP, unknown flags [cause the script to exit with an error
code|https://github.com/apache/cordova-wp8/blob/master/wp8/template/cordova/lib/deploy.js#L324-L326].
On Android and iOS,the expected behaviour is matched.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6265) CLI guide omits Windows workstations using CLI for Android projects
[
https://issues.apache.org/jira/browse/CB-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948322#comment-13948322
]
Michael Brooks commented on CB-6265:
[~cmarcelk] I'm using v1.0.1 from daringfireball.net:
{code}
$ markdown -v
This is Markdown, version 1.0.1.
Copyright 2004 John Gruber
http://daringfireball.net/projects/markdown/
{code}
However, it appears that I've installed it via brew:
{code}
$ brew info markdown
markdown: stable 1.0.1
http://daringfireball.net/projects/markdown/
{code}
You can install it on OS X with:
{code}
$ sudo brew install markdown
{code}
CLI guide omits Windows workstations using CLI for Android projects
---
Key: CB-6265
URL: https://issues.apache.org/jira/browse/CB-6265
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 3.2.0
Reporter: Marcel Kinard
Assignee: Marcel Kinard
Priority: Minor
Fix For: 3.5.0
In
http://cordova.apache.org/docs/en/3.4.0/guide_cli_index.md.html#The%20Command-Line%20Interface
it has the following line for Android:
Android (Mac, Linux)
Windows is obviously missing. Appears to be a defect in the docs going back
to 3.2.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6265) CLI guide omits Windows workstations using CLI for Android projects
[ https://issues.apache.org/jira/browse/CB-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935603#comment-13935603 ] Michael Brooks commented on CB-6265: [~cmarcelk] I'm using nokogiri 1.5.6 as well. Two reasons that come to mind on why you may see so many altered files: 1. Did you update the cordova-website repository before running the rsync? 2. Have the docs added a new version or language? Both would update the upper-right selection box on every page of every version. CLI guide omits Windows workstations using CLI for Android projects --- Key: CB-6265 URL: https://issues.apache.org/jira/browse/CB-6265 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.2.0 Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: 3.5.0 In http://cordova.apache.org/docs/en/3.4.0/guide_cli_index.md.html#The%20Command-Line%20Interface it has the following line for Android: Android (Mac, Linux) Windows is obviously missing. Appears to be a defect in the docs going back to 3.2. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5666) Add Ubuntu Platform Guide Documentation
[ https://issues.apache.org/jira/browse/CB-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-5666. Resolution: Fixed Fix Version/s: 3.3.0 Add Ubuntu Platform Guide Documentation --- Key: CB-5666 URL: https://issues.apache.org/jira/browse/CB-5666 Project: Apache Cordova Issue Type: Improvement Components: Docs, Ubuntu Affects Versions: 3.3.0 Reporter: Michael Brooks Assignee: Michael Brooks Fix For: 3.3.0 Add the initial documentation for Cordova-Ubuntu. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CB-5528) Link to Upgrading BlackBerry10
[ https://issues.apache.org/jira/browse/CB-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837098#comment-13837098 ] Michael Brooks commented on CB-5528: Looks good [~jsoref]! Link to Upgrading BlackBerry10 -- Key: CB-5528 URL: https://issues.apache.org/jira/browse/CB-5528 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry, Docs Affects Versions: 3.0.0, 3.1.0, 3.2.0 Reporter: Josh Soref Assignee: Josh Soref Fix For: 3.1.0 While there is an Upgrading document for BlackBerry10 in the Guide, there's no link for it, and hasn't been since the beginning (3.0) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5419) feature param name=onload not documented on Android
[ https://issues.apache.org/jira/browse/CB-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-5419. Resolution: Fixed Fix Version/s: 2.4.0 feature param name=onload not documented on Android - Key: CB-5419 URL: https://issues.apache.org/jira/browse/CB-5419 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Reporter: Axel Nennker Assignee: Michael Brooks Fix For: 2.4.0 Plugins are only instanciated when the cordava app's JS code first call them. If the plugin needs to be notified of a e.g. a hardware event or some other intent filter its onNewIntent method is never called unless onload = true. feature ... ... param name=onload value=true / /feature is a neded for all plugins that react to operating system events. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5178) [Release + 3.2.0] Change default docs to new version
[ https://issues.apache.org/jira/browse/CB-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-5178. Resolution: Fixed Updated docs.cordova.io to redirect to version 3.2.0. [Release + 3.2.0] Change default docs to new version Key: CB-5178 URL: https://issues.apache.org/jira/browse/CB-5178 Project: Apache Cordova Issue Type: Sub-task Components: Android, App Hello World, BlackBerry, CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Windows 8, WP8 Reporter: Steve Gill Assignee: Michael Brooks Fix For: 3.2.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5290) Launch images for all devices must include the status bar region.
[ https://issues.apache.org/jira/browse/CB-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817456#comment-13817456 ] Michael Brooks commented on CB-5290: Thanks [~lmnbeyond]! I've merged your work and also updated the [PhoneGap Wiki on Splash Screen Sizes|https://github.com/phonegap/phonegap/wiki/App-Splash-Screen-Sizes]. Launch images for all devices must include the status bar region. - Key: CB-5290 URL: https://issues.apache.org/jira/browse/CB-5290 Project: Apache Cordova Issue Type: Bug Components: Docs, iOS Affects Versions: 3.1.0 Reporter: lmnbeyond Fix For: 3.2.0 According to iOS Human Interface Guidelines: Create launch images in different sizes for different devices. Launch images for all devices must include the status bar region. Create launch images in the following sizes: For iPhone 5 and iPod touch (5th generation): 640 x 1136 pixels For other iPhone and iPod touch devices: 640 x 960 pixels 320 x 480 pixels (standard resolution) For iPad portrait: 1536 x 2048 pixels 768 x 1024 pixels (standard resolution) For iPad landscape: 2048 x 1536 pixels 1024 x 768 pixels (standard resolution) https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/LaunchImages.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5290) Launch images for all devices must include the status bar region.
[ https://issues.apache.org/jira/browse/CB-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks reassigned CB-5290: -- Assignee: Michael Brooks Launch images for all devices must include the status bar region. - Key: CB-5290 URL: https://issues.apache.org/jira/browse/CB-5290 Project: Apache Cordova Issue Type: Bug Components: Docs, iOS Affects Versions: 3.1.0 Reporter: lmnbeyond Assignee: Michael Brooks Fix For: 3.2.0 According to iOS Human Interface Guidelines: Create launch images in different sizes for different devices. Launch images for all devices must include the status bar region. Create launch images in the following sizes: For iPhone 5 and iPod touch (5th generation): 640 x 1136 pixels For other iPhone and iPod touch devices: 640 x 960 pixels 320 x 480 pixels (standard resolution) For iPad portrait: 1536 x 2048 pixels 768 x 1024 pixels (standard resolution) For iPad landscape: 2048 x 1536 pixels 1024 x 768 pixels (standard resolution) https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/LaunchImages.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5290) Launch images for all devices must include the status bar region.
[ https://issues.apache.org/jira/browse/CB-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-5290. Resolution: Fixed Launch images for all devices must include the status bar region. - Key: CB-5290 URL: https://issues.apache.org/jira/browse/CB-5290 Project: Apache Cordova Issue Type: Bug Components: Docs, iOS Affects Versions: 3.1.0 Reporter: lmnbeyond Assignee: Michael Brooks Fix For: 3.2.0 According to iOS Human Interface Guidelines: Create launch images in different sizes for different devices. Launch images for all devices must include the status bar region. Create launch images in the following sizes: For iPhone 5 and iPod touch (5th generation): 640 x 1136 pixels For other iPhone and iPod touch devices: 640 x 960 pixels 320 x 480 pixels (standard resolution) For iPad portrait: 1536 x 2048 pixels 768 x 1024 pixels (standard resolution) For iPad landscape: 2048 x 1536 pixels 1024 x 768 pixels (standard resolution) https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/LaunchImages.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813105#comment-13813105 ] Michael Brooks commented on CB-3962: Sure. I'll review the commits from [pull request #143|https://github.com/apache/cordova-docs/pull/143] and let you know when it's all merged. document and implement editorial guidelines --- Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[
https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813181#comment-13813181
]
Michael Brooks commented on CB-3962:
Alright, it's all merged.
Commits 8e4f91f88340e89f714fdcbdc9af3031be338532 and
f76c6310039af02bc4850139542868b999583b26 had conflicts with
{{docs/en/edge/guide/cli/index.md}}. It looks as though this branch's CLI
document is either ahead or behind the master CLI document. In the master, the
Cordova and Project upgrades are combined. In your branch, they are separated.
document and implement editorial guidelines
---
Key: CB-3962
URL: https://issues.apache.org/jira/browse/CB-3962
Project: Apache Cordova
Issue Type: Task
Components: Docs
Reporter: Mike Sierra
Assignee: Mike Sierra
Priority: Critical
The top-level STYLESHEET.md file collects editorial guidelines to help
standardize the doc. Keep updating to reflect any site-side conventions.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811373#comment-13811373 ] Michael Brooks commented on CB-3962: There is a [third way|http://xkcd.com/1285/]. document and implement editorial guidelines --- Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811470#comment-13811470 ] Michael Brooks commented on CB-3962: Yea, I like the idea of using icons to represent platforms when it makes sense. document and implement editorial guidelines --- Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4890) Reference to plugins.xml should be config.xml
[
https://issues.apache.org/jira/browse/CB-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809692#comment-13809692
]
Michael Brooks commented on CB-4890:
Nice catch.
Reference to plugins.xml should be config.xml
-
Key: CB-4890
URL: https://issues.apache.org/jira/browse/CB-4890
Project: Apache Cordova
Issue Type: Improvement
Components: Docs
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Michael Brooks
Priority: Trivial
The Capture API documentation for Android (see Permissions section) is
still referring to plugins.xml instead of config.xml
{quote}
Permissions
Android
app/res/xml/plugins.xml
{quote}
http://cordova.apache.org/docs/en/2.9.0/cordova_media_capture_capture.md.html#Capture
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4881) Update Docs Plugin-Plist Section
[ https://issues.apache.org/jira/browse/CB-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772873#comment-13772873 ] Michael Brooks commented on CB-4881: Nice catch. I've added your commit (see above). Update Docs Plugin-Plist Section Key: CB-4881 URL: https://issues.apache.org/jira/browse/CB-4881 Project: Apache Cordova Issue Type: Task Components: Docs Affects Versions: 3.0.0 Environment: Plugman build system Reporter: Burke Holland Priority: Minor Labels: docs Original Estimate: 1h Remaining Estimate: 1h The docs currently describe the plugin-plist section as deprecated, but then go on to describe adding a plugin under the config-file section of the XML in an incorrect way. It should be... feature name=LocalStorage param name=ios-package value=CDVLocalStorage / /feature ...per the article at http://cordova.apache.org/docs/en/3.0.0/guide_platforms_ios_plugin.md.html#iOS%20Plugins -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4811) Device plugin requires no permissions, so remove from documentaion
[
https://issues.apache.org/jira/browse/CB-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766752#comment-13766752
]
Michael Brooks commented on CB-4811:
Thanks for the update [~mrbillau]!
I'm hesitant to merge this update without verification from a second person...
and I'm not the one to do it.
[~bowserj] can you confirm that {{uses-permission
android:name=android.permission.READ_PHONE_STATE /}} is not required for
Android's cordova-plugin-device?
Device plugin requires no permissions, so remove from documentaion
---
Key: CB-4811
URL: https://issues.apache.org/jira/browse/CB-4811
Project: Apache Cordova
Issue Type: Bug
Components: Docs, Plugin Device
Affects Versions: 3.0.0
Environment: Windows 7
Reporter: Mike Billau
Assignee: Michael Brooks
Priority: Minor
The docs for the cordova-plugin-device plugin
(http://cordova.apache.org/docs/en/edge/cordova_device_device.md.html#Device)
say that the plugin will add
uses-permission android:name=android.permission.READ_PHONE_STATE /
to AndroidManifest.xml
However, it seems like this is not actually the case, because 1) there is
nothing in the plugin.xml file that would do this (missing config-file
target=AndroidManifest.xml parent=/*[...]) element, and 2) it doesn't
seem like the device functionality needs this permission at all.
Unless there are some strange dependencies that I'm not seeing between other
plugins that require the device plugin to have this permission (that wouldn't
make sense...?), I think the docs should be edited to reflect this to avoid
causing confusion (it confused me at least!)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4784) French language translation needs consistent heading naming -- links currently broken
[ https://issues.apache.org/jira/browse/CB-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765626#comment-13765626 ] Michael Brooks commented on CB-4784: Merged [pull request 110|https://github.com/apache/cordova-docs/pull/110]. French language translation needs consistent heading naming -- links currently broken - Key: CB-4784 URL: https://issues.apache.org/jira/browse/CB-4784 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Michael Brooks Priority: Minor See: http://cordova.apache.org/docs/fr/edge/index.html Notice that the major elements are NOT links. This is because the naming of the headers is not consistent between the index page and each individual subpage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4783) Korean language translation needs consistent heading naming -- links currently broken
[ https://issues.apache.org/jira/browse/CB-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765625#comment-13765625 ] Michael Brooks commented on CB-4783: Merged [pull request 110|https://github.com/apache/cordova-docs/pull/110]. Korean language translation needs consistent heading naming -- links currently broken - Key: CB-4783 URL: https://issues.apache.org/jira/browse/CB-4783 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor See: http://cordova.apache.org/docs/ko/edge/index.html Notice that the major elements are NOT links. This is because the naming of the headers is not consistent between the index page and each individual subpage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4773) Remove older version of Japanese documentation jp
[ https://issues.apache.org/jira/browse/CB-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4773. Resolution: Fixed Commit https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=e7168dd7e82a8aab11a01117413dfd91486e029e Remove older version of Japanese documentation jp --- Key: CB-4773 URL: https://issues.apache.org/jira/browse/CB-4773 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Michael Brooks Priority: Trivial We already have both of those translations with the abbreviations of kr and jp but I just noticed that the standard language codes are ko and ja. Removing the jp from the docs directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4644) File API documentation - FileReader headings are incorrect
[ https://issues.apache.org/jira/browse/CB-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747299#comment-13747299 ] Michael Brooks commented on CB-4644: Thanks for submitting all of these documentation issues, [~dinglemouse]. I really appreciate your attention to detail. File API documentation - FileReader headings are incorrect -- Key: CB-4644 URL: https://issues.apache.org/jira/browse/CB-4644 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Michael Brooks Priority: Minor Many the headings in the *FileReader* section are incorrect and/or inconsistent with other sections making it difficult to read For example, * Read As Data URL - this is a function name. Heading should be readAsDataURL * Quick Example for readAsDataURL - should be h3 not h2 * Abort Quick Example - should be h2 abort (because it is a function name) * This abort section seems misplaced - it is currently between the Quick and Full example for readAsText? * Quick Example should be h3. * Read As Text - this is a function name. Heading should be readAsText * Quick Example for readAsText - should be h3 not h2 * Full Example for readAsText - should be h3 instead of h2 * iOS Quirks for readAsText - should be h3 not h2 * Read As Binary String - this is a function name. Heading should be readAsBinaryString * Quick Example for readAsBinaryString - should be h3 not h2 * Read As Array Buffer - this is a function name. Heading should be readAsArrayBuffer * Quick Example for readAsArrayBuffer - should be h3 not h2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4527) Unix and Windows Scripts should both be included in a project
Michael Brooks created CB-4527:
--
Summary: Unix and Windows Scripts should both be included in a
project
Key: CB-4527
URL: https://issues.apache.org/jira/browse/CB-4527
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 3.0.0
Reporter: Michael Brooks
Assignee: Joe Bowser
**Problem:**
When a new Android project is created, only the OS-specific the
platform-scripts ({{my-project/cordova/}}) are copied over.
For example, on Windows only the batch files are copied; on Unix only the bash
files are copied.
**Solution:**
Both sets of scripts should be copied.
Many projects involve multiple collaborators. On Android, it is not uncommon
for those collaborators to use both Windows and Unix. So, the generated Android
project should support both environments.
**Reference:**
[phonegap/phonegap-cli#136|https://github.com/phonegap/phonegap-cli/issues/136#issuecomment-22238361]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4515) Allow CLI to specify emulator target details
Michael Brooks created CB-4515: -- Summary: Allow CLI to specify emulator target details Key: CB-4515 URL: https://issues.apache.org/jira/browse/CB-4515 Project: Apache Cordova Issue Type: Improvement Components: CLI Affects Versions: 3.0.0 Reporter: Michael Brooks Assignee: Filip Maj *Overview:* A feature request of the PhoneGap CLI is to specify the type of iOS emulator. For example, launching with the iPad instead of the iPhone. *Current State:* At the moment, it looks as though the iOS emulate script [can support this operation|https://github.com/apache/cordova-ios/blob/master/bin/templates/project/cordova/emulate#L38], but it is non-standard across all of the platform scripts. *Reference:* [phonegap/phonegap#144|https://github.com/phonegap/phonegap-cli/issues/144] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4517) Evaluate -force_load linker flag instead of -all_load
[
https://issues.apache.org/jira/browse/CB-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks resolved CB-4517.
Resolution: Duplicate
Awesome, thanks Shaz!
Evaluate -force_load linker flag instead of -all_load
-
Key: CB-4517
URL: https://issues.apache.org/jira/browse/CB-4517
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 3.0.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
*Overview:*
There is an outstanding PhoneGap pull request to update the linker flag.
According to the author, {{-all_load}} is bad practice and breaks other SDKs
with Objective-C categories.
You can read more about it here:
http://stackoverflow.com/questions/2906147/what-does-the-all-load-linker-flag-do
*Reference:*
https://github.com/phonegap/phonegap/pull/34#issuecomment-22155597
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4483) Route Debug Console Messages to Terminal
Michael Brooks created CB-4483:
--
Summary: Route Debug Console Messages to Terminal
Key: CB-4483
URL: https://issues.apache.org/jira/browse/CB-4483
Project: Apache Cordova
Issue Type: New Feature
Components: CLI
Affects Versions: Master
Reporter: Michael Brooks
Assignee: Filip Maj
*Feature:*
Display {{console.x}} messages in the terminal when using the CLI.
Emit {{console.x}} messages as an event when using the module.
*Reason:*
Currently, the debug messages go to different sources depending on the
platform. By implementing this feature, the terminal can become the unified
location for all debug messages are displayed.
Additionally, any tools built on top of the CLI can route the debug messages to
their own destination (e.g. a Sublime plugin).
*Reference:*
[PhoneGap Google Groups
Thread|https://groups.google.com/forum/#!topic/phonegap/Z377GJtAIiE]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4461) Globalozation and I18N - Crowdin Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727117#comment-13727117 ] Michael Brooks commented on CB-4461: Very nice! Globalozation and I18N - Crowdin Proposal Discussion - Key: CB-4461 URL: https://issues.apache.org/jira/browse/CB-4461 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor Labels: documentation, globalization, translation, I have created a project within Transifex for cordova here: https://www.transifex.com/projects/p/cordova The way it works is: 1.files are upload  to the Transifex system.  Transifex does not have markdown files as one of the options for file type to import but they do have html and plain text.  I have chosen plain text for testing and it appears to work great.  I setup a preferences for the resource to be pulled from github on a daily basis with the latest version of the file. 2.Users may come in and provide translation or all or part of a file. 3.A maintainer or language expert is assigned to each language and approves the translations 4.progress information and status can be shown per file/project.  Once complete, the translated file can be uploaded back into github under the specific language.  This part is a manual process Other open source projects use Transifex, for example, OpenStack.  I propose we do the following: Use Transifex for each major release starting with 3.0.  If it is relatively easy to translate for minor releases we can vote to do so with each. Assign a language maintainer for each supported language to monitor translations. I suggest we start with Spanish and French since those are the languages our group of committers can best contribute to at this time.  (If we have a consensus to use Transfix, please volunteer if you'd like to be the maintainer for a specific language). Once a section of the documentation is approved by the language moderator, we push the updates to GitHub. Another thing to think about, Transifex offers automatic translation for faster translation using google translation services or microsoft's which require an api key and a paid subscription.  I don't know if either of those companies offer a free key for open source needs. I know we have a few representatives from those companies that might be able to give us more information. Why we should be worried about translation? Globalization! If we can attract more developers to Cordova and make it easier for those developers to get up and running with cordova by providing documentation in their native languages,  cordova will continue to grow in popularity globally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4485) Command line build ignoring content src in config.xml settings
[
https://issues.apache.org/jira/browse/CB-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727319#comment-13727319
]
Michael Brooks commented on CB-4485:
[~bowserj] that CLI doesn't copy the icons or splashscreens to the correct area.
[~filmaj] and I have discussed this a few times. The fact is that it is much
easier for the CLI (node.js) to do this task compared to the platform-scripts.
However, we know from experience that platforms need to take responsibility for
their tasks, otherwise the whole system becomes brittle.
My current thought is that we can implement this feature with the CLI and work
with the platform-scripts later. As a platform supports {{config.xml}}
definitions, we can remove them from the CLI.
Command line build ignoring content src in config.xml settings
--
Key: CB-4485
URL: https://issues.apache.org/jira/browse/CB-4485
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0
Environment: Windows 8 x64
Reporter: Joshua McFarland
Assignee: Michael Brooks
I have specifically set the content src, but when building the application is
still uses the default of 'index.html' rather than what I have set. It's not
entirely ignoring the config file, because if I change the app name or id it
does get properly updated on build.
content src=index-cordova.html /
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-4485) Command line build ignoring content src in config.xml settings
[
https://issues.apache.org/jira/browse/CB-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13727319#comment-13727319
]
Michael Brooks edited comment on CB-4485 at 8/2/13 4:40 AM:
[~bowserj] - the CLI doesn't copy the icons or splashscreens to the correct
area.
[~filmaj] and I have discussed this a few times. The fact is that it is much
easier for the CLI (node.js) to do this task compared to the platform-scripts.
However, we know from experience that platforms need to take responsibility for
their tasks, otherwise the whole system becomes brittle.
My current thought is that we can implement this feature with the CLI and work
with the platform-scripts later. As a platform supports {{config.xml}}
definitions, we can remove them from the CLI.
was (Author: mwbrooks):
[~bowserj] that CLI doesn't copy the icons or splashscreens to the correct
area.
[~filmaj] and I have discussed this a few times. The fact is that it is much
easier for the CLI (node.js) to do this task compared to the platform-scripts.
However, we know from experience that platforms need to take responsibility for
their tasks, otherwise the whole system becomes brittle.
My current thought is that we can implement this feature with the CLI and work
with the platform-scripts later. As a platform supports {{config.xml}}
definitions, we can remove them from the CLI.
Command line build ignoring content src in config.xml settings
--
Key: CB-4485
URL: https://issues.apache.org/jira/browse/CB-4485
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0
Environment: Windows 8 x64
Reporter: Joshua McFarland
Assignee: Michael Brooks
I have specifically set the content src, but when building the application is
still uses the default of 'index.html' rather than what I have set. It's not
entirely ignoring the config file, because if I change the app name or id it
does get properly updated on build.
content src=index-cordova.html /
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4324) Upgrading Guides on front page goes to itself
[ https://issues.apache.org/jira/browse/CB-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4324. Resolution: Fixed Fix Version/s: 3.1.0 Upgrading Guides on front page goes to itself - Key: CB-4324 URL: https://issues.apache.org/jira/browse/CB-4324 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Environment: Half of the Upgrading Guides gets highlighted (just Guides) There is a Guides item in the sidebar as well, that just goes to itself (the parent header is Guides also) Reporter: Shazron Abdullah Assignee: Michael Brooks Fix For: 3.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4324) Upgrading Guides on front page goes to itself
[ https://issues.apache.org/jira/browse/CB-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725663#comment-13725663 ] Michael Brooks commented on CB-4324: Thanks for the patch [~quiqueg]! I've applied your work as [commit 64e56d|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=64e56d4bdc4efe5911587479111fbb16e0919762]. Upgrading Guides on front page goes to itself - Key: CB-4324 URL: https://issues.apache.org/jira/browse/CB-4324 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Environment: Half of the Upgrading Guides gets highlighted (just Guides) There is a Guides item in the sidebar as well, that just goes to itself (the parent header is Guides also) Reporter: Shazron Abdullah Assignee: Michael Brooks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3762) notification.prompt doesn't accept an empty string for default text
[ https://issues.apache.org/jira/browse/CB-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725675#comment-13725675 ] Michael Brooks commented on CB-3762: I've applied the cordova-docs patch as commit [717182|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=717182904485303df0fe392a8043d5dfb61f335e]. Can someone please review and apply the JS fix. notification.prompt doesn't accept an empty string for default text --- Key: CB-3762 URL: https://issues.apache.org/jira/browse/CB-3762 Project: Apache Cordova Issue Type: Bug Components: Plugin Dialogs Affects Versions: 2.7.0, 2.8.0 Reporter: Todd Miller Assignee: mike billau Priority: Minor Fix For: 3.1.0 Specifying as the last parameter for navigator.notification.prompt, the prompt dialog will still show Default Text in the text input box. However, putting a string of just a single space works (but also results in a space in the text box). In additional seems like the default of Default Text isn't the best choice from UX perspective. A default of an empty text box would make more sense. Changing line 5909 in cordova.js from: var _defaultText = (defaultText || Default text); to var _defaultText = (defaultText || ); Resolves the issue and gives a blank text box by default. Documentation would also need to be updated with the new default if this is adopted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4316) Android library not getting properly downloaded/installed
[
https://issues.apache.org/jira/browse/CB-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725692#comment-13725692
]
Michael Brooks commented on CB-4316:
[~filmaj] this is actually a deeper problem from my experiences on the
[phonegap-cli/issues|https://github.com/mwbrooks/phonegap-cli/issues/].
The one scenario that we are familiar with is a corrupt library because it was
lazy-loaded when the native SDK was not properly configured. The common culprit
is Android building the {{jar}}. The solution to this is to properly configure
the SDK environment, delete the lazy-loaded library, and try building again.
Things usually work fine.
The other scenario is that the lazy-load fails in some manner and the extracted
directory is empty. See issue
[phonegap-cli/issues/121|https://github.com/mwbrooks/phonegap-cli/issues/121]
for an example with the Hello World app. The solution is still the same -
delete and try again. However, this appears to be due to a bad network
connection (perhaps on Apache's end).
Android library not getting properly downloaded/installed
-
Key: CB-4316
URL: https://issues.apache.org/jira/browse/CB-4316
Project: Apache Cordova
Issue Type: Bug
Components: Android, CLI
Affects Versions: 3.0.0
Environment: Windows 8
Reporter: Benjamin Clot
Assignee: Michael Brooks
This a follow-up to [this
issue|https://github.com/mwbrooks/phonegap-cli/issues/77#issuecomment-21170828]
on the PhoneGap CLI GitHub.
Basically, after running {{cordova --verbose platform add android}}, I get
downloading url and requesting url but then it stops and I only have a
{{%userdir%\.cordova\lib\android\cordova\3.0.0rc1\cordova-android-3.0.0rc1-25bb215}}
directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4426) Create app doesn't work if computer cannot connect to github and raises exception instead of showing friendly error message
[ https://issues.apache.org/jira/browse/CB-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks reassigned CB-4426: -- Assignee: Filip Maj (was: Michael Brooks) Create app doesn't work if computer cannot connect to github and raises exception instead of showing friendly error message --- Key: CB-4426 URL: https://issues.apache.org/jira/browse/CB-4426 Project: Apache Cordova Issue Type: Bug Components: App Hello World, CLI Affects Versions: 3.0.0 Reporter: Simone Chiaretta Assignee: Filip Maj i just installed phonegap 3.0 and tried to create a new app via the CLI: phonegap create my-app But I get the following error: [phonegap] downloading https://github.com/phonegap/phonegap-app-hello-world/archive/3.0.0.tar.gz... TypeError: Cannot read property 'length' of undefined at Request.request.get.pipe.pipe.tar.Extract.path [as _callback] (C:\Documen ts and Settings\CHIARSI\Application Data\npm\node_modules\phonegap\node_modules\cordova\src\lazy_load.js:70:78) at self.callback (C:\Documents and Settings\CHIARSI\Application Data\npm\node_modules\phonegap\node_modules\cordova\node_modules\request\index.js:148:22) at Request.EventEmitter.emit (events.js:117:20) at ClientRequest.self.clientErrorHandler (C:\Documents and Settings\CHIARSI\Application Data\npm\node_modules\phonegap\node_modules\cordova\node_modules\request\index.js:257:10) at ClientRequest.EventEmitter.emit (events.js:95:17) at CleartextStream.socketErrorListener (http.js:1528:9) at CleartextStream.EventEmitter.emit (events.js:95:17) at Socket.onerror (tls.js:1424:17) at Socket.EventEmitter.emit (events.js:117:20) at net.js:441:14 I have the impression the phonegap command line utility doesn't read properly the proxy configuration of windows, and this is due to some mishandling of the error. So, I posted this message, first to report this small bug, and second to ask how can I set proxy configuration for the phonegap utility. Or if there is a workaround to this in case proxy cannot be set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4425) Upgrading Guides heading on home page has broken link
[ https://issues.apache.org/jira/browse/CB-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724220#comment-13724220 ] Michael Brooks commented on CB-4425: This is already resolved. The website just hasn't been updated. Upgrading Guides heading on home page has broken link - Key: CB-4425 URL: https://issues.apache.org/jira/browse/CB-4425 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Filip Maj Assignee: Michael Brooks Priority: Critical Fix For: 3.1.0 http://cordova.apache.org/docs/en/3.0.0/ note the broken link for upgrading guides right in the middle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4425) Upgrading Guides heading on home page has broken link
[ https://issues.apache.org/jira/browse/CB-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4425. Resolution: Fixed Upgrading Guides heading on home page has broken link - Key: CB-4425 URL: https://issues.apache.org/jira/browse/CB-4425 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Filip Maj Assignee: Michael Brooks Priority: Critical Fix For: 3.1.0 http://cordova.apache.org/docs/en/3.0.0/ note the broken link for upgrading guides right in the middle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4414) guide link is not working of apache cordova 3.0 documentation
[ https://issues.apache.org/jira/browse/CB-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724222#comment-13724222 ] Michael Brooks commented on CB-4414: I believe this has already been fixed. The problem is that website hasn't been updated because it is a manual process that we do each release. You can see the latest documentation on http://docs.phonegap.com to have a preview of what the Cordova docs will looks like. guide link is not working of apache cordova 3.0 documentation - Key: CB-4414 URL: https://issues.apache.org/jira/browse/CB-4414 Project: Apache Cordova Issue Type: Improvement Components: Website Affects Versions: 3.0.0 Reporter: Prateek Jaiswal Following link is not working : http://cordova.apache.org/docs/en/3.0.0/index.md.html#Guides Error 404 : page not found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4414) guide link is not working of apache cordova 3.0 documentation
[ https://issues.apache.org/jira/browse/CB-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4414. Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Michael Brooks guide link is not working of apache cordova 3.0 documentation - Key: CB-4414 URL: https://issues.apache.org/jira/browse/CB-4414 Project: Apache Cordova Issue Type: Improvement Components: Website Affects Versions: 3.0.0 Reporter: Prateek Jaiswal Assignee: Michael Brooks Fix For: 3.1.0 Following link is not working : http://cordova.apache.org/docs/en/3.0.0/index.md.html#Guides Error 404 : page not found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4461) Globalozation and I18N - Transifex Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724504#comment-13724504 ] Michael Brooks commented on CB-4461: This is a pretty neat service. So, currently we store language translations in separate directories. Can Transifex support this approach? By the sounds of it, it's a manual step so we can massage the filesystem to work? If I understand correctly, we are not actually buying into the Transifex service. Instead, it is an interface to our documentation in the same way that GitHub is an interface to our source code. Globalozation and I18N - Transifex Proposal Discussion --- Key: CB-4461 URL: https://issues.apache.org/jira/browse/CB-4461 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor Labels: documentation, globalization, translation, I have created a project within Transifex for cordova here: https://www.transifex.com/projects/p/cordova The way it works is: 1.files are upload  to the Transifex system.  Transifex does not have markdown files as one of the options for file type to import but they do have html and plain text.  I have chosen plain text for testing and it appears to work great.  I setup a preferences for the resource to be pulled from github on a daily basis with the latest version of the file. 2.Users may come in and provide translation or all or part of a file. 3.A maintainer or language expert is assigned to each language and approves the translations 4.progress information and status can be shown per file/project.  Once complete, the translated file can be uploaded back into github under the specific language.  This part is a manual process Other open source projects use Transifex, for example, OpenStack.  I propose we do the following: Use Transifex for each major release starting with 3.0.  If it is relatively easy to translate for minor releases we can vote to do so with each. Assign a language maintainer for each supported language to monitor translations. I suggest we start with Spanish and French since those are the languages our group of committers can best contribute to at this time.  (If we have a consensus to use Transfix, please volunteer if you'd like to be the maintainer for a specific language). Once a section of the documentation is approved by the language moderator, we push the updates to GitHub. Another thing to think about, Transifex offers automatic translation for faster translation using google translation services or microsoft's which require an api key and a paid subscription.  I don't know if either of those companies offer a free key for open source needs. I know we have a few representatives from those companies that might be able to give us more information. Why we should be worried about translation? Globalization! If we can attract more developers to Cordova and make it easier for those developers to get up and running with cordova by providing documentation in their native languages,  cordova will continue to grow in popularity globally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3465) Android Upgrade Documentation
[
https://issues.apache.org/jira/browse/CB-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724523#comment-13724523
]
Michael Brooks commented on CB-3465:
What's the problem here? Are we just missing the Android upgrade documentation
for {{2.5.0=2.6.0}} and {{2.6.0=2.7.0}}?
Android Upgrade Documentation
-
Key: CB-3465
URL: https://issues.apache.org/jira/browse/CB-3465
Project: Apache Cordova
Issue Type: Bug
Components: Android, Docs
Affects Versions: 2.6.0, 2.7.0
Reporter: Doug Millasich
Assignee: Michael Brooks
Fix For: 3.1.0
The upgrade descriptions for both Upgrade to 2.6.0 from 2.5.0 and Upgrade
to 2.7.0 from 2.6.0 has been removed from the documentation guides. I know
it was there - recently, but it's been removed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4461) Globalozation and I18N - Transifex Proposal Discussion
[ https://issues.apache.org/jira/browse/CB-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724559#comment-13724559 ] Michael Brooks commented on CB-4461: Cool, well let's try it out! There's no harm if it's not adopted. Globalozation and I18N - Transifex Proposal Discussion --- Key: CB-4461 URL: https://issues.apache.org/jira/browse/CB-4461 Project: Apache Cordova Issue Type: Improvement Components: Docs Affects Versions: 3.0.0 Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor Labels: documentation, globalization, translation, I have created a project within Transifex for cordova here: https://www.transifex.com/projects/p/cordova The way it works is: 1.files are upload  to the Transifex system.  Transifex does not have markdown files as one of the options for file type to import but they do have html and plain text.  I have chosen plain text for testing and it appears to work great.  I setup a preferences for the resource to be pulled from github on a daily basis with the latest version of the file. 2.Users may come in and provide translation or all or part of a file. 3.A maintainer or language expert is assigned to each language and approves the translations 4.progress information and status can be shown per file/project.  Once complete, the translated file can be uploaded back into github under the specific language.  This part is a manual process Other open source projects use Transifex, for example, OpenStack.  I propose we do the following: Use Transifex for each major release starting with 3.0.  If it is relatively easy to translate for minor releases we can vote to do so with each. Assign a language maintainer for each supported language to monitor translations. I suggest we start with Spanish and French since those are the languages our group of committers can best contribute to at this time.  (If we have a consensus to use Transfix, please volunteer if you'd like to be the maintainer for a specific language). Once a section of the documentation is approved by the language moderator, we push the updates to GitHub. Another thing to think about, Transifex offers automatic translation for faster translation using google translation services or microsoft's which require an api key and a paid subscription.  I don't know if either of those companies offer a free key for open source needs. I know we have a few representatives from those companies that might be able to give us more information. Why we should be worried about translation? Globalization! If we can attract more developers to Cordova and make it easier for those developers to get up and running with cordova by providing documentation in their native languages,  cordova will continue to grow in popularity globally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3465) Android Upgrade Documentation
[ https://issues.apache.org/jira/browse/CB-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724562#comment-13724562 ] Michael Brooks commented on CB-3465: Hi [~dmillasich], Thanks for checking the docs and ensuring that everything's kosher. I'll go ahead and resolve the issue. If you notice something amiss in the next release, just reopen it and nudge me! Android Upgrade Documentation - Key: CB-3465 URL: https://issues.apache.org/jira/browse/CB-3465 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.6.0, 2.7.0 Reporter: Doug Millasich Assignee: Michael Brooks Fix For: 3.1.0 Attachments: compose-unknown-contact.jpg The upgrade descriptions for both Upgrade to 2.6.0 from 2.5.0 and Upgrade to 2.7.0 from 2.6.0 has been removed from the documentation guides. I know it was there - recently, but it's been removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3465) Android Upgrade Documentation
[ https://issues.apache.org/jira/browse/CB-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-3465. Resolution: Fixed Android Upgrade Documentation - Key: CB-3465 URL: https://issues.apache.org/jira/browse/CB-3465 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.6.0, 2.7.0 Reporter: Doug Millasich Assignee: Michael Brooks Fix For: 3.1.0 Attachments: compose-unknown-contact.jpg The upgrade descriptions for both Upgrade to 2.6.0 from 2.5.0 and Upgrade to 2.7.0 from 2.6.0 has been removed from the documentation guides. I know it was there - recently, but it's been removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4423) BlackBerry create script fails when App ID has special characters
Michael Brooks created CB-4423:
--
Summary: BlackBerry create script fails when App ID has special
characters
Key: CB-4423
URL: https://issues.apache.org/jira/browse/CB-4423
Project: Apache Cordova
Issue Type: Bug
Components: BlackBerry
Affects Versions: 3.0.0
Reporter: Michael Brooks
Assignee: Lorin Beer
*Problem:*
The following error is generated when a new project has an App ID with a
special character:
{{code}}
An error occured during creation of blackberry10 sub-project. App ID must be
sequence of alpha-numeric (optionally seperated by '.') characters, no longer
than 50 characters
{{code}}
*Suggestion:*
The special character requirement may be a limitation of the BlackBerry SDK.
However, Cordova allows projects to include these characters.
The create script should gracefully handle the special character by removing or
replacing them.
*Related issues:*
- [phonegap-cli#119|https://github.com/mwbrooks/phonegap-cli/issues/119]
-
[phonegap-app-hello-world#1|https://github.com/phonegap/phonegap-app-hello-world/issues/1]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4347) [BlackBerry10] Restore improvements to platform guide
[ https://issues.apache.org/jira/browse/CB-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723278#comment-13723278 ] Michael Brooks commented on CB-4347: You need to generate the documentation and then publish the website with the latest documentation. Generate the docs using `./bin/generate`. You can also speed up process by only generating 3.0.0 or edge with `./bin/generate en 3.0.0` or `./bin/generate en edge`. Update the site by moving the generate docs from `cordova-docs/public/en/VERSION` to `cordova-website/public/docs/en/VERSION`. Then commit. Each commit will auto-public. The site README.md has more details on how to publish [1]. If you don't have the magic Ruby version to generate the docs or site, then I can do it for you. Just ask :) [1] https://svn.apache.org/repos/asf/cordova/site/ [BlackBerry10] Restore improvements to platform guide - Key: CB-4347 URL: https://issues.apache.org/jira/browse/CB-4347 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Bryan Higgins Assignee: Michael Brooks Priority: Blocker Fix For: 3.0.0 [~mwbrooks] [~sierra] It looks like some really great updates to the BB10 platform guide (including screen shots) were lost with this commit: https://github.com/apache/cordova-docs/commit/2d175336c4776fa8bfd402660224b8ef67ae7190 We then added instructions on how to configure the SDK tools paths here: https://github.com/apache/cordova-docs/commit/847dd84b572e92ee9c62c2444b3360d85656db55 But that got reverted in the very next commit: https://github.com/apache/cordova-docs/commit/5f2f472625a309b4c2a0f5c953f42853698f39bb We need to be careful with merge commits. By the looks of it, there may be issues with some of the other platforms as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4347) [BlackBerry10] Restore improvements to platform guide
[ https://issues.apache.org/jira/browse/CB-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723355#comment-13723355 ] Michael Brooks commented on CB-4347: woo! [BlackBerry10] Restore improvements to platform guide - Key: CB-4347 URL: https://issues.apache.org/jira/browse/CB-4347 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Bryan Higgins Assignee: Michael Brooks Priority: Blocker Fix For: 3.0.0 [~mwbrooks] [~sierra] It looks like some really great updates to the BB10 platform guide (including screen shots) were lost with this commit: https://github.com/apache/cordova-docs/commit/2d175336c4776fa8bfd402660224b8ef67ae7190 We then added instructions on how to configure the SDK tools paths here: https://github.com/apache/cordova-docs/commit/847dd84b572e92ee9c62c2444b3360d85656db55 But that got reverted in the very next commit: https://github.com/apache/cordova-docs/commit/5f2f472625a309b4c2a0f5c953f42853698f39bb We need to be careful with merge commits. By the looks of it, there may be issues with some of the other platforms as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4386) iOS Platform Guide CLI example uses 'android'
[ https://issues.apache.org/jira/browse/CB-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719769#comment-13719769 ] Michael Brooks commented on CB-4386: Thanks for the nudge [~ldeluca]! I have a call with [~sierra] shortly, so I'll review and merge your work while I go over his latest pull request. iOS Platform Guide CLI example uses 'android' - Key: CB-4386 URL: https://issues.apache.org/jira/browse/CB-4386 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Bruce Lefebvre Assignee: Lisa Seacat DeLuca Priority: Trivial At [0], (Open a Project in the SDK section): $ cordova platform add android Should be: $ cordova platform add ios [0] http://docs.phonegap.com/en/3.0.0/guide_platforms_ios_index.md.html#iOS%20Platform%20Guide_open_a_project_in_the_sdk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4386) iOS Platform Guide CLI example uses 'android'
[ https://issues.apache.org/jira/browse/CB-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719856#comment-13719856 ] Michael Brooks commented on CB-4386: Looks good [~ldeluca]. I've cherry-picked your work and updated [pull request #84|https://github.com/apache/cordova-docs/pull/84]. iOS Platform Guide CLI example uses 'android' - Key: CB-4386 URL: https://issues.apache.org/jira/browse/CB-4386 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.0.0 Reporter: Bruce Lefebvre Assignee: Lisa Seacat DeLuca Priority: Trivial At [0], (Open a Project in the SDK section): $ cordova platform add android Should be: $ cordova platform add ios [0] http://docs.phonegap.com/en/3.0.0/guide_platforms_ios_index.md.html#iOS%20Platform%20Guide_open_a_project_in_the_sdk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4307) CLONE - CLONE - Tag Docs
[ https://issues.apache.org/jira/browse/CB-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4307. Resolution: Fixed CLONE - CLONE - Tag Docs Key: CB-4307 URL: https://issues.apache.org/jira/browse/CB-4307 Project: Apache Cordova Issue Type: Sub-task Components: Docs Reporter: Steve Gill Assignee: Michael Brooks Fix For: 3.0.0 This should wait until all other repos are tagged. Steps: 1. Look through all open JIRA bugs targeted at the current version and either fix or postpone them. 2. Update snapshot of docs using the release branch, then cherry-pick that into master. 3. Ensure docs are up-to-date by looking through the changelogs on all platforms (or at least cordova-js). 4. Tag (via coho) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712678#comment-13712678 ] Michael Brooks commented on CB-3962: The above commit is from [pull request #77|https://github.com/apache/cordova-docs/pull/77]. document and implement editorial guidelines --- Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (CB-3816) Add CLI Guide
[ https://issues.apache.org/jira/browse/CB-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks updated CB-3816: --- Comment: was deleted (was: The above commit is from [pull request #76|https://github.com/apache/cordova-docs/pull/76].) Add CLI Guide - Key: CB-3816 URL: https://issues.apache.org/jira/browse/CB-3816 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Reader wants to be able to use CLI for as much of the development cycle as possible, or bootstrap a project to hand off to SDK(s), or some combo. Clarify: which platforms are supported under which OS you can run each. Tutorial should generate default HelloCordova app, adds platforms, view in emulator(s), then view on device(s). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4220) CLONE - Tag Docs
[ https://issues.apache.org/jira/browse/CB-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712708#comment-13712708 ] Michael Brooks commented on CB-4220: We've postponed the upgrade guides that were delaying this release. [Tag 3.0.0rc1|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=17ffa3e527678e1ee21860d72352d815acef0fa9]. CLONE - Tag Docs Key: CB-4220 URL: https://issues.apache.org/jira/browse/CB-4220 Project: Apache Cordova Issue Type: Sub-task Components: Docs Reporter: Filip Maj Assignee: Michael Brooks This should wait until all other repos are tagged. Steps: 1. Look through all open JIRA bugs targeted at the current version and either fix or postpone them. 2. Update snapshot of docs using the release branch, then cherry-pick that into master. 3. Ensure docs are up-to-date by looking through the changelogs on all platforms (or at least cordova-js). 4. Tag (via coho) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4220) CLONE - Tag Docs
[ https://issues.apache.org/jira/browse/CB-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-4220. Resolution: Fixed CLONE - Tag Docs Key: CB-4220 URL: https://issues.apache.org/jira/browse/CB-4220 Project: Apache Cordova Issue Type: Sub-task Components: Docs Reporter: Filip Maj Assignee: Michael Brooks This should wait until all other repos are tagged. Steps: 1. Look through all open JIRA bugs targeted at the current version and either fix or postpone them. 2. Update snapshot of docs using the release branch, then cherry-pick that into master. 3. Ensure docs are up-to-date by looking through the changelogs on all platforms (or at least cordova-js). 4. Tag (via coho) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710217#comment-13710217 ] Michael Brooks commented on CB-3822: The above commits are from [pull request #69|https://github.com/apache/cordova-docs/pull/69]. Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710254#comment-13710254 ] Michael Brooks commented on CB-3822: The above commit is from [pull request #72|https://github.com/apache/cordova-docs/pull/72]. Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710258#comment-13710258 ] Michael Brooks commented on CB-3822: The above commit is from [pull request #73|https://github.com/apache/cordova-docs/pull/73]. Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3962) document and implement editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710276#comment-13710276 ] Michael Brooks commented on CB-3962: The above commits are from [pull request #74|https://github.com/apache/cordova-docs/pull/74]. document and implement editorial guidelines --- Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4080) modify CSS to improve presentation
[ https://issues.apache.org/jira/browse/CB-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710279#comment-13710279 ] Michael Brooks commented on CB-4080: Added commits from [pull request #75|https://github.com/apache/cordova-docs/pull/75]. modify CSS to improve presentation -- Key: CB-4080 URL: https://issues.apache.org/jira/browse/CB-4080 Project: Apache Cordova Issue Type: Bug Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Minor Metabug for anything that improves the skin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3816) Add CLI Guide
[ https://issues.apache.org/jira/browse/CB-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710284#comment-13710284 ] Michael Brooks commented on CB-3816: The above commit is from [pull request #76|https://github.com/apache/cordova-docs/pull/76]. Add CLI Guide - Key: CB-3816 URL: https://issues.apache.org/jira/browse/CB-3816 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Reader wants to be able to use CLI for as much of the development cycle as possible, or bootstrap a project to hand off to SDK(s), or some combo. Clarify: which platforms are supported under which OS you can run each. Tutorial should generate default HelloCordova app, adds platforms, view in emulator(s), then view on device(s). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4224) CLONE - Update Upgrading Guide for 2.7.0 - 2.8.0 for Windows Phone 7/8
[ https://issues.apache.org/jira/browse/CB-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks reassigned CB-4224: -- Assignee: Jesse MacFadyen (was: Michael Brooks) CLONE - Update Upgrading Guide for 2.7.0 - 2.8.0 for Windows Phone 7/8 --- Key: CB-4224 URL: https://issues.apache.org/jira/browse/CB-4224 Project: Apache Cordova Issue Type: Sub-task Components: Docs, WP7, WP8 Reporter: Filip Maj Assignee: Jesse MacFadyen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4261) cordova.plugin('list') should fire callback on success
Michael Brooks created CB-4261:
--
Summary: cordova.plugin('list') should fire callback on success
Key: CB-4261
URL: https://issues.apache.org/jira/browse/CB-4261
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Michael Brooks
*Problem:*
Currently, the {{cordova.plugin('list', [], fn);}} does not trigger the
callback on a success.
*Expectation:*
The function should trigger the callback on a success and pass the plugins
found.
The callback signature should be:
{code}
function(e, plugins) {}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4261) cordova.plugin('list') should fire callback on success
[
https://issues.apache.org/jira/browse/CB-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks resolved CB-4261.
Resolution: Fixed
Fix Version/s: 2.9.0
cordova.plugin('list') should fire callback on success
--
Key: CB-4261
URL: https://issues.apache.org/jira/browse/CB-4261
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Michael Brooks
Fix For: 2.9.0
*Problem:*
Currently, the {{cordova.plugin('list', [], fn);}} does not trigger the
callback on a success.
*Expectation:*
The function should trigger the callback on a success and pass the plugins
found.
The callback signature should be:
{code}
function(e, plugins) {}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4199) iOS Platform Script `run --device` uses Simulator
[
https://issues.apache.org/jira/browse/CB-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708125#comment-13708125
]
Michael Brooks commented on CB-4199:
The issue [phonegap-cli#94|https://github.com/mwbrooks/phonegap-cli/issues/94]
contains a usage example where the user ran into this unexpected behaviour.
iOS Platform Script `run --device` uses Simulator
-
Key: CB-4199
URL: https://issues.apache.org/jira/browse/CB-4199
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
On iOS, the platform script {{./cordova/run --device}} deploys to the
simulator.
This is incorrect and unexpected behaviour.
Since iOS cannot deploy to a device (yet), it should do nothing, return an
error code, and explain that devices are not yet supported. This is helpful
to both users and utilities using the platform script.
This is also an important feature for {{cordova-cli}} and {{phonegap-cli}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4199) iOS Platform Script `run --device` uses Simulator
[
https://issues.apache.org/jira/browse/CB-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708247#comment-13708247
]
Michael Brooks commented on CB-4199:
[~shazron] - ah, well oddly the {{cordova-cli}} assumes that {{--device}} is
implemented in all of the platforms. I suppose we should test and ensure it
works everywhere :)
According to the wiki article, [error code 1 - not implemented / unsupported
command|http://wiki.apache.org/cordova/CommandLineToolingDesign#Errors].
iOS Platform Script `run --device` uses Simulator
-
Key: CB-4199
URL: https://issues.apache.org/jira/browse/CB-4199
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
On iOS, the platform script {{./cordova/run --device}} deploys to the
simulator.
This is incorrect and unexpected behaviour.
Since iOS cannot deploy to a device (yet), it should do nothing, return an
error code, and explain that devices are not yet supported. This is helpful
to both users and utilities using the platform script.
This is also an important feature for {{cordova-cli}} and {{phonegap-cli}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4199) iOS Platform Script `run --device` uses Simulator
[
https://issues.apache.org/jira/browse/CB-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708249#comment-13708249
]
Michael Brooks commented on CB-4199:
Thanks Shaz!
iOS Platform Script `run --device` uses Simulator
-
Key: CB-4199
URL: https://issues.apache.org/jira/browse/CB-4199
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
Fix For: 3.0.0
On iOS, the platform script {{./cordova/run --device}} deploys to the
simulator.
This is incorrect and unexpected behaviour.
Since iOS cannot deploy to a device (yet), it should do nothing, return an
error code, and explain that devices are not yet supported. This is helpful
to both users and utilities using the platform script.
This is also an important feature for {{cordova-cli}} and {{phonegap-cli}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3849) review, reference, and expose new content
[ https://issues.apache.org/jira/browse/CB-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707185#comment-13707185 ] Michael Brooks commented on CB-3849: The above commit is from [pull request #70|https://github.com/apache/cordova-docs/pull/70] review, reference, and expose new content - Key: CB-3849 URL: https://issues.apache.org/jira/browse/CB-3849 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical Once new section of doc is mature, review it for accuracy. If it's OK, make sure any otherwise commented cross references are enabled. Also make sure the top-level splash screen references the content. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-4182) Long delays when lazy-loading some libraries
Michael Brooks created CB-4182:
--
Summary: Long delays when lazy-loading some libraries
Key: CB-4182
URL: https://issues.apache.org/jira/browse/CB-4182
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Filip Maj
*Problem:*
When lazy-loading certain libraries, the node process can hang after the
completion callback is fired. This delay can take up to a few minutes, but is
usually ~30 seconds.
*tar.gz Files:*
Apache {{tar.gz}} files do not experience long delays.
GitHub {{tar.gz}} files do experience long delays.
You can reproduce this issue by using the
[github.com/apache/cordova-app-hello-world/achive/2.9.0.tar.gzip|https://github.com/apache/cordova-app-hello-world/archive/2.9.0.tar.gz]
file instead of the default served by Apache GitWeb.
*Hosting:*
The web host does not affect this issue. I have hosted the Apache file and the
GitHub file on my own web server (S3) and experienced the same results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4182) Long delays when lazy-loading some libraries
[
https://issues.apache.org/jira/browse/CB-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706286#comment-13706286
]
Michael Brooks commented on CB-4182:
Additional information about this issue can be found on
[phonegap-cli#85|https://github.com/mwbrooks/phonegap-cli/issues/85].
Long delays when lazy-loading some libraries
-
Key: CB-4182
URL: https://issues.apache.org/jira/browse/CB-4182
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 2.9.0
Reporter: Michael Brooks
Assignee: Filip Maj
*Problem:*
When lazy-loading certain libraries, the node process can hang after the
completion callback is fired. This delay can take up to a few minutes, but is
usually ~30 seconds.
*tar.gz Files:*
Apache {{tar.gz}} files do not experience long delays.
GitHub {{tar.gz}} files do experience long delays.
You can reproduce this issue by using the
[github.com/apache/cordova-app-hello-world/achive/2.9.0.tar.gzip|https://github.com/apache/cordova-app-hello-world/archive/2.9.0.tar.gz]
file instead of the default served by Apache GitWeb.
*Hosting:*
The web host does not affect this issue. I have hosted the Apache file and
the GitHub file on my own web server (S3) and experienced the same results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4074) Error when adding android platform on Windows 7
[
https://issues.apache.org/jira/browse/CB-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704746#comment-13704746
]
Michael Brooks commented on CB-4074:
Awesome, it looks as though [~textoo] has figured out one issue. Anyone running
into this in the future should try to first delete their
{{~/.cordova/lib/android/cordova/2.9.0/}} directory. The download may have been
corrupt or the library may have been installed with permissions that the
regular user cannot read.
I'm leaving this issue open for [~ldeluca]'s issue around the Android SDK.
For what it's worth, I am using the Android ADT-Bundle on Windows 7. It appears
to be the only SDK download option.
[~ldeluca] can you run either of these commands from the command-line:
- {{android -h}}
- {{android list target}}
Error when adding android platform on Windows 7
---
Key: CB-4074
URL: https://issues.apache.org/jira/browse/CB-4074
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Environment: Windows 7
Reporter: Lisa Seacat DeLuca
Assignee: Benn Mapes
I got past the issue where I wasn't able to install cordova on my windows 7
machine. I create a new project just fine but when I tried to add android as
a platform I see the following error:
C:\workspaces\cordovacli\helloworldcordova platform add android
shell.js: internal error
Error: EPERM, operation not permitted
'C:\Users\me\.cordova\lib\android\cordova\2.9.0\cordova-android-2.9.0-df1536e\test'
at Object.fs.renameSync (fs.js:543:18)
at
C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:487:8
at Array.forEach (native)
at Object._mv
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:463:11)
at Object.mv
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:1471:23)
at Extract.anonymous
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\src\lazy_load.js:115:43)
at Extract.EventEmitter.emit (events.js:117:20)
at DirWriter.anonymous
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\lib\extract.js:66:8)
at DirWriter.EventEmitter.emit (events.js:117:20)
at end
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\node_modules\fstream\lib\writer.js:323:12)
--
note: I can use eclipse and create an android project with no problem and
test on devices and emulators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-4074) Error when adding android platform on Windows 7
[ https://issues.apache.org/jira/browse/CB-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks reassigned CB-4074: -- Assignee: Filip Maj (was: Benn Mapes) Error when adding android platform on Windows 7 --- Key: CB-4074 URL: https://issues.apache.org/jira/browse/CB-4074 Project: Apache Cordova Issue Type: Bug Components: CLI Environment: Windows 7 Reporter: Lisa Seacat DeLuca Assignee: Filip Maj I got past the issue where I wasn't able to install cordova on my windows 7 machine. I create a new project just fine but when I tried to add android as a platform I see the following error: C:\workspaces\cordovacli\helloworldcordova platform add android shell.js: internal error Error: EPERM, operation not permitted 'C:\Users\me\.cordova\lib\android\cordova\2.9.0\cordova-android-2.9.0-df1536e\test' at Object.fs.renameSync (fs.js:543:18) at C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:487:8 at Array.forEach (native) at Object._mv (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:463:11) at Object.mv (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:1471:23) at Extract.anonymous (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\src\lazy_load.js:115:43) at Extract.EventEmitter.emit (events.js:117:20) at DirWriter.anonymous (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\lib\extract.js:66:8) at DirWriter.EventEmitter.emit (events.js:117:20) at end (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\node_modules\fstream\lib\writer.js:323:12) -- note: I can use eclipse and create an android project with no problem and test on devices and emulators. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4074) Error when adding android platform on Windows 7
[
https://issues.apache.org/jira/browse/CB-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701261#comment-13701261
]
Michael Brooks commented on CB-4074:
Arg! Android builds successfully on my Windows 7 Ultimate N (64bit).
I also tried projects with special characters, such as capitals, dots, and
dashes.
Do you guys see anything else unique with [~textoo]'s stack trace? {{E:\}}
perhaps?
Error when adding android platform on Windows 7
---
Key: CB-4074
URL: https://issues.apache.org/jira/browse/CB-4074
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Environment: Windows 7
Reporter: Lisa Seacat DeLuca
Assignee: Benn Mapes
I got past the issue where I wasn't able to install cordova on my windows 7
machine. I create a new project just fine but when I tried to add android as
a platform I see the following error:
C:\workspaces\cordovacli\helloworldcordova platform add android
shell.js: internal error
Error: EPERM, operation not permitted
'C:\Users\me\.cordova\lib\android\cordova\2.9.0\cordova-android-2.9.0-df1536e\test'
at Object.fs.renameSync (fs.js:543:18)
at
C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:487:8
at Array.forEach (native)
at Object._mv
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:463:11)
at Object.mv
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:1471:23)
at Extract.anonymous
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\src\lazy_load.js:115:43)
at Extract.EventEmitter.emit (events.js:117:20)
at DirWriter.anonymous
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\lib\extract.js:66:8)
at DirWriter.EventEmitter.emit (events.js:117:20)
at end
(C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\node_modules\fstream\lib\writer.js:323:12)
--
note: I can use eclipse and create an android project with no problem and
test on devices and emulators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-4074) Error when adding android platform on Windows 7
[ https://issues.apache.org/jira/browse/CB-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701040#comment-13701040 ] Michael Brooks commented on CB-4074: I'm also downloading a Win7 image, but it will take me a while to setup the VM and try to reproduce the issue. Windows! Error when adding android platform on Windows 7 --- Key: CB-4074 URL: https://issues.apache.org/jira/browse/CB-4074 Project: Apache Cordova Issue Type: Bug Components: CLI Environment: Windows 7 Reporter: Lisa Seacat DeLuca Assignee: Benn Mapes I got past the issue where I wasn't able to install cordova on my windows 7 machine. I create a new project just fine but when I tried to add android as a platform I see the following error: C:\workspaces\cordovacli\helloworldcordova platform add android shell.js: internal error Error: EPERM, operation not permitted 'C:\Users\me\.cordova\lib\android\cordova\2.9.0\cordova-android-2.9.0-df1536e\test' at Object.fs.renameSync (fs.js:543:18) at C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:487:8 at Array.forEach (native) at Object._mv (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:463:11) at Object.mv (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\shelljs\shell.js:1471:23) at Extract.anonymous (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\src\lazy_load.js:115:43) at Extract.EventEmitter.emit (events.js:117:20) at DirWriter.anonymous (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\lib\extract.js:66:8) at DirWriter.EventEmitter.emit (events.js:117:20) at end (C:\Users\me\AppData\Roaming\npm\node_modules\cordova\node_modules\tar\node_modules\fstream\lib\writer.js:323:12) -- note: I can use eclipse and create an android project with no problem and test on devices and emulators. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3962) document editorial guidelines
[ https://issues.apache.org/jira/browse/CB-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701039#comment-13701039 ] Michael Brooks commented on CB-3962: The above commit is from [pull request #67|https://github.com/apache/cordova-docs/pull/67]. document editorial guidelines - Key: CB-3962 URL: https://issues.apache.org/jira/browse/CB-3962 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical The top-level STYLESHEET.md file collects editorial guidelines to help standardize the doc. Keep updating to reflect any site-side conventions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699245#comment-13699245 ] Michael Brooks commented on CB-3822: The above two commits are from [pull request #63|https://github.com/apache/cordova-docs/pull/63]. Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13698251#comment-13698251 ] Michael Brooks commented on CB-3822: The above commits are from [pull request #59|https://github.com/apache/cordova-docs/pull/59]. Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-3770) can't install cordova CLI on Win7
[
https://issues.apache.org/jira/browse/CB-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13698318#comment-13698318
]
Michael Brooks edited comment on CB-3770 at 7/2/13 10:09 PM:
-
Commit
[39c290|https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=39c2903]
removes the {{git}} dependency and downloads {{filmaj/node-xcode}} as a HTTP
tarball.
was (Author: mwbrooks):
Commit
[39c290|https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=39c2903]
removes the {{git}} dependency and downloaded {{filmaj/node-xcode}} as a HTTP
tarball.
can't install cordova CLI on Win7
-
Key: CB-3770
URL: https://issues.apache.org/jira/browse/CB-3770
Project: Apache Cordova
Issue Type: Bug
Components: CLI, Docs
Affects Versions: 2.8.0
Environment: Win7
Reporter: Mike Sierra
Assignee: Benn Mapes
Priority: Minor
Run npm install -g cordova on Win7 machine with WinPhone7 SDK installed.
Fails to install. According to Benn, Seems to just be an error inside the
ripple-emulator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-4060) npm dependency references a git repository
[
https://issues.apache.org/jira/browse/CB-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks resolved CB-4060.
Resolution: Fixed
Assignee: Michael Brooks (was: Filip Maj)
npm dependency references a git repository
--
Key: CB-4060
URL: https://issues.apache.org/jira/browse/CB-4060
Project: Apache Cordova
Issue Type: Bug
Components: Plugman
Environment:
https://github.com/apache/cordova-plugman/blob/master/package.json#L23
Reporter: Michael Brooks
Assignee: Michael Brooks
*Problem:*
{{npm}} throws a {{ENOGIT}} error when installing the {{plugman}} module on a
system that does not have git installed.
This is a common scenario on a Windows machine, where many users will use
_node.js command prompt_ to interact with node applications. In order to
access git, the user must use _GitBash command prompt_ or add git to their
_node.js command prompt_ {{PATH}}.
*Reason:*
The {{package.json}} references the {{git}} repository
[filmaj/node-xcode|https://github.com/apache/cordova-plugman/blob/master/package.json#L23].
*Solution:*
The {{package.json}} should reference a published node module or a standard
HTTP address that references a tarball.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3985) Tag Docs
[ https://issues.apache.org/jira/browse/CB-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694304#comment-13694304 ] Michael Brooks commented on CB-3985: Commit and tag 2.9.0: commit [9d1529|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=9d152990701292fe7fb6e1961a3c5ba93b201a62] Tag Docs Key: CB-3985 URL: https://issues.apache.org/jira/browse/CB-3985 Project: Apache Cordova Issue Type: Sub-task Components: Docs Reporter: Andrew Grieve Assignee: Michael Brooks 1. Ensure docs are generated and up-to-date 2. Tag: ./cordova-coho/coho prepare-release-branch --version 2.9.0 -r docs ./cordova-coho/coho repo-status -r docs -b master -b 2.9.x # If changes look right: ./cordova-coho/coho repo-push -r docs -b master -b 2.9.x ./cordova-coho/coho tag-release --version 2.9.0 -r docs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3985) Tag Docs
[ https://issues.apache.org/jira/browse/CB-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-3985. Resolution: Fixed Fix Version/s: 2.9.0 Tag Docs Key: CB-3985 URL: https://issues.apache.org/jira/browse/CB-3985 Project: Apache Cordova Issue Type: Sub-task Components: Docs Reporter: Andrew Grieve Assignee: Michael Brooks Fix For: 2.9.0 1. Ensure docs are generated and up-to-date 2. Tag: ./cordova-coho/coho prepare-release-branch --version 2.9.0 -r docs ./cordova-coho/coho repo-status -r docs -b master -b 2.9.x # If changes look right: ./cordova-coho/coho repo-push -r docs -b master -b 2.9.x ./cordova-coho/coho tag-release --version 2.9.0 -r docs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3356) Clarify version number used in Getting Started screen caps
[ https://issues.apache.org/jira/browse/CB-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690648#comment-13690648 ] Michael Brooks commented on CB-3356: Hi [~mrbillau], JIRA issues are always welcome! It's the best way to keep all of our moving parts organized. Thanks for the pull request, I've cherry-picked your commit. Clarify version number used in Getting Started screen caps -- Key: CB-3356 URL: https://issues.apache.org/jira/browse/CB-3356 Project: Apache Cordova Issue Type: Bug Components: Docs Environment: Windows Phone 8 Reporter: mike billau Assignee: Michael Brooks Labels: documentation Fix For: Master Original Estimate: 0.5h Remaining Estimate: 0.5h Hello, I have received some reports that users are getting confused when following the Getting Started guides because the version number on the screen caps is old. This might end up changing when we switch to cordova.js instead of cordova-x.x.x.js but until then I think a clarification note is a good idea. This already exists on iOS and I did not see any screen caps for the other guides that have cordova.js shown, so I think it's only an issue for WP8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3356) Clarify version number used in Getting Started screen caps
[ https://issues.apache.org/jira/browse/CB-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Brooks resolved CB-3356. Resolution: Fixed Clarify version number used in Getting Started screen caps -- Key: CB-3356 URL: https://issues.apache.org/jira/browse/CB-3356 Project: Apache Cordova Issue Type: Bug Components: Docs Environment: Windows Phone 8 Reporter: mike billau Assignee: Michael Brooks Labels: documentation Fix For: Master Original Estimate: 0.5h Remaining Estimate: 0.5h Hello, I have received some reports that users are getting confused when following the Getting Started guides because the version number on the screen caps is old. This might end up changing when we switch to cordova.js instead of cordova-x.x.x.js but until then I think a clarification note is a good idea. This already exists on iOS and I did not see any screen caps for the other guides that have cordova.js shown, so I think it's only an issue for WP8. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3822) Rework SDK-specific content
[ https://issues.apache.org/jira/browse/CB-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690773#comment-13690773 ] Michael Brooks commented on CB-3822: The above commits are from [pull request #54|https://github.com/apache/cordova-docs/pull/54] Rework SDK-specific content --- Key: CB-3822 URL: https://issues.apache.org/jira/browse/CB-3822 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Organize platform-specific content as fixed set of unnumbered subheads listed below. Remove or move information extraneous to that core set of content. Remove out-of-scope redundant references to installing cordova or creating projects; link CLI doc. For platforms not covered by the CLI, remove any unnecessary references to non-CLI command-line tools from main exposition; append summary in Command-line Utilities. Subheads: Requirements and Support Install the SDK Open a Project in the SDK Deploy to Emulator [from CLI within SDK] Deploy to Device [from CLI within SDK] Common Problems [hopefully optional] Command-line Utilities -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3827) Modify content structure
[ https://issues.apache.org/jira/browse/CB-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690779#comment-13690779 ] Michael Brooks commented on CB-3827: The above two commits are from [pull request #57|https://github.com/apache/cordova-docs/pull/57]. Modify content structure Key: CB-3827 URL: https://issues.apache.org/jira/browse/CB-3827 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Restructure as follows: 1 Guides 1.1 Overview 1.2 The Cordova Command-line Interface 1.3 Platform Guides 1.3.1 FOO Platform Guide 1.3.2 FOO Plugins 1.3.3 FOO Command-line Utilities 1.3.4 Upgrading FOO 1.4 API and Configuration Guide 1.4.1 Modifying Preferences 1.4.2 Basic Interaction 1.4.3 Device Sensors 1.4.4 Data Access 1.4.5 Network and Storage 1.4.6 Globalization 1.4.7 Domain Whitelisting 1.4.8 Privacy Guidelines 1.5 Extended Hybrid Applications 1.5.1 Opening a Browser Window 1.5.2 Embedding a WebView 1.5.3 Adding a Plug-in [references various FOO Plugins] 1.6 Distributing Applications 2 Reference 2.1 API Reference 2.1.x [each API...] 2.2 Configuration Reference 2.2.1 Shared Configuration Settings 2.2.2 iOS Configuration 2.2.3 Android Configuration 2.2.4 Blackberry Configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
