[jira] [Created] (CB-5289) Medic. Can't be installed on Windows due to ios-deploy dependency
Sergey Grebnov created CB-5289: -- Summary: Medic. Can't be installed on Windows due to ios-deploy dependency Key: CB-5289 URL: https://issues.apache.org/jira/browse/CB-5289 Project: Apache Cordova Issue Type: Bug Components: Medic Environment: Windows Reporter: Sergey Grebnov Assignee: Sergey Grebnov Due to 'ios-deploy' reference Medic can't be installed on Windows platform. We should use special installation script to check for current platform and install platform specific dependencies as suggested here http://stackoverflow.com/questions/15176082/npm-package-json-os-specific-dependency/15670089#15670089 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5288) Support fuzzy matching when using "cordova plugin add"
lmnbeyond created CB-5288: - Summary: Support fuzzy matching when using "cordova plugin add" Key: CB-5288 URL: https://issues.apache.org/jira/browse/CB-5288 Project: Apache Cordova Issue Type: Improvement Components: CLI Affects Versions: 3.1.0 Reporter: lmnbeyond It would be more convenient if cli supports fuzzy matching. For example: $ cordova plugin add device Please select, 1: org.apache.cordova.device 2: org.apache.cordova.device-motion 3: org.apache.cordova.device-orientation 4: quit What now> 1 Fetching plugin from "org.apache.cordova.device"... Starting installation of "org.apache.cordova.device" for ios Preparing ios project org.apache.cordova.device installed on ios. What do you guys think ;) ? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4749) "cordova prepare" doesn't give a good error message when run not from a cordova project
[ https://issues.apache.org/jira/browse/CB-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Koudritsky resolved CB-4749. - Resolution: Fixed > "cordova prepare" doesn't give a good error message when run not from a > cordova project > --- > > Key: CB-4749 > URL: https://issues.apache.org/jira/browse/CB-4749 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Andrew Grieve >Assignee: Mark Koudritsky >Priority: Minor > > $ cordova prepare > [TypeError: Arguments to path.join must be strings] -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5287) Upgrade from 2.9.7 to 3.1.0 platform add error
Kevin Vilbig created CB-5287: Summary: Upgrade from 2.9.7 to 3.1.0 platform add error Key: CB-5287 URL: https://issues.apache.org/jira/browse/CB-5287 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.1.0, 3.0.0 Environment: uname -a Linux localhost.localdomain 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux CentOS Reporter: Kevin Vilbig Priority: Blocker I'm working with a project that builds on Cordova 2.9.7, but when I updated to the latest version via npm and the instructions provided[1], it breaks like so. [1]http://cordova.apache.org/docs/en/3.1.0/guide_platforms_android_upgrading.md.html#Upgrading%20Android $cordova platform add android [Error: An error occured during creation of android sub-project. Creating Cordova project for the Android platform: Path: platforms/android Package: com.my.project Name: myProject Android target: android-17 Copying template files... shell.js: internal error Error: EROFS, read-only file system 'platforms/android/cordova/node_modules/.bin/shjs' at Object.fs.symlinkSync (fs.js:730:18) at cpdirSyncRecursive (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/node_modules/shelljs/shell.js:1575:10) at cpdirSyncRecursive (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/node_modules/shelljs/shell.js:1572:7) at /home/kevin/.cordova/lib/android/cordova/3.1.0/bin/node_modules/shelljs/shell.js:325:9 at Array.forEach (native) at Object._cp (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/node_modules/shelljs/shell.js:302:11) at Object.cp (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/node_modules/shelljs/shell.js:1491:23) at copyScripts (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js:86:11) at /home/kevin/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js:184:9 at setShellFatal (/home/kevin/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js:48:5) I attempted the upgrade directions a couple times, so I don't think I missed a step. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4863) Drop iOS 5.0 support
[
https://issues.apache.org/jira/browse/CB-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814382#comment-13814382
]
Shazron Abdullah commented on CB-4863:
--
Default template:
1. *Select* "Project -> Build Settings -> Architectures -> Architectures ->
*Standard Architectures (including 64-bit)*"
CordovaLib:
1. *Select* "Project -> Build Settings -> Architectures -> Architectures ->
*Debug* -> iphoneos7.* SDK -> Standard Architectures (including 64-bit)"
2. *Select* "Project -> Build Settings -> Architectures -> Architectures ->
*Release* -> iphoneos7.* SDK -> Standard Architectures (including 64-bit)"
3. Add *arm64* to "Project -> Build Settings -> Architectures -> *Valid
Architectures*"
> Drop iOS 5.0 support
>
>
> Key: CB-4863
> URL: https://issues.apache.org/jira/browse/CB-4863
> Project: Apache Cordova
> Issue Type: Improvement
> Components: iOS
>Affects Versions: 3.0.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
>Priority: Minor
> Labels: ios7
>
> Adding this issue for discussion.
> We still support iOS 5.0 in the Deployment Target.
> iOS 6.0 and greater support enables arm64 support (64-bit) but not sure of
> any advantages there, really.
> Also, this is consistent with our previous support where we only support the
> current iOS version and one version back. Also, finding a device with iOS 5
> support (besides the iPad 1, which cannot have iOS 6 support) is becoming
> problematic.
> iOS 6 API diffs from 5:
> https://developer.apple.com/library/ios/releasenotes/General/iOS60APIDiffs/index.html
> Apple's note regarding 64-bit support:
> https://developer.apple.com/news/index.php?id=9162013a
> {quote}
> If you wish to continue to support iOS 6 then you will need to build for
> 32-bit only. Next month we will be making changes that will allow you to
> create a single app binary that supports 32-bit on iOS 6, as well as 32-bit
> and 64-bit on iOS 7.
> {quote}
> So, based on that I think if we go ahead and support arm64 we wait for this
> 64-bit iOS fat binary functionality coming "next month". This probably will
> coincide with their Mavericks 10.9 OS and SDK release with the new
> accompanying Xcode bump.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5286) Fix warnings when compiled under arm64
Shazron Abdullah created CB-5286: Summary: Fix warnings when compiled under arm64 Key: CB-5286 URL: https://issues.apache.org/jira/browse/CB-5286 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: Master Reporter: Shazron Abdullah Priority: Minor Depends on CB-4863 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CB-4863) Drop iOS 5.0 support
[
https://issues.apache.org/jira/browse/CB-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813264#comment-13813264
]
Shazron Abdullah edited comment on CB-4863 at 11/5/13 10:36 PM:
arm64 fat binary support is here with Xcode 5.01:
http://lists.apple.com/archives/xcode-users/2013/Nov/msg00010.html (iOS 5.1.1
minimum deployment support though, bumped up)
was (Author: shazron):
arm64 fat binary support is here with Xcode 5.01:
http://lists.apple.com/archives/xcode-users/2013/Nov/msg00010.html (5.1.1
minimum deployment support though, bumped up)
> Drop iOS 5.0 support
>
>
> Key: CB-4863
> URL: https://issues.apache.org/jira/browse/CB-4863
> Project: Apache Cordova
> Issue Type: Improvement
> Components: iOS
>Affects Versions: 3.0.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
>Priority: Minor
> Labels: ios7
>
> Adding this issue for discussion.
> We still support iOS 5.0 in the Deployment Target.
> iOS 6.0 and greater support enables arm64 support (64-bit) but not sure of
> any advantages there, really.
> Also, this is consistent with our previous support where we only support the
> current iOS version and one version back. Also, finding a device with iOS 5
> support (besides the iPad 1, which cannot have iOS 6 support) is becoming
> problematic.
> iOS 6 API diffs from 5:
> https://developer.apple.com/library/ios/releasenotes/General/iOS60APIDiffs/index.html
> Apple's note regarding 64-bit support:
> https://developer.apple.com/news/index.php?id=9162013a
> {quote}
> If you wish to continue to support iOS 6 then you will need to build for
> 32-bit only. Next month we will be making changes that will allow you to
> create a single app binary that supports 32-bit on iOS 6, as well as 32-bit
> and 64-bit on iOS 7.
> {quote}
> So, based on that I think if we go ahead and support arm64 we wait for this
> 64-bit iOS fat binary functionality coming "next month". This probably will
> coincide with their Mavericks 10.9 OS and SDK release with the new
> accompanying Xcode bump.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5128) Add new meta data to plugins.xml
[ https://issues.apache.org/jira/browse/CB-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814341#comment-13814341 ] Braden Shepherdson commented on CB-5128: Are there any plugins left to do, or can this issue be closed? > Add new meta data to plugins.xml > > > Key: CB-5128 > URL: https://issues.apache.org/jira/browse/CB-5128 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Battery Status, Plugin Camera, Plugin Console, > Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device > Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin > Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin > Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin > Vibration, Plugman >Reporter: Steve Gill >Assignee: Herm Wong > Fix For: 3.2.0 > > > Rep tag -> points to repo location > Issues tag (maybe tracker tag) -> points to issue tracker (for jira, link > should have component) > Docs tag (if applicable) -> points to docs location > Description tag -> short summary (might not be necessary if we decide to > output the readme on plugins.cordova.io for each plugin) > Home Page Link (if applicable) -> points to the plugin home page (not > applicable for cordova core plugins) > Author tag -> make it compatible with package.json author tag. Plugin.xml > gets converted to a package.json when you run the publish command. > Keywords? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5218) config.json should also carry the the engine information
[
https://issues.apache.org/jira/browse/CB-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814340#comment-13814340
]
Braden Shepherdson commented on CB-5218:
Which file is this? $PROJECT/.cordova/config.json? $HOME/.cordova/config.json?
I don't really understand what this bug is asking for. I'm beginning to wonder,
given the frequency with which "I copied the project between machines and it's
no longer working" bugs are turning up, if we shouldn't build a "cordova
squash" and "cordova expand" or whatever that can bundle up an app, with the
necessary metadata to re-create it captured in some special file by the tools,
which the expanding side can read and use to install the right versions of the
various platforms and plugins.
> config.json should also carry the the engine information
>
>
> Key: CB-5218
> URL: https://issues.apache.org/jira/browse/CB-5218
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI
>Affects Versions: 3.1.0
>Reporter: Gorkem ERCAN
>
> CLI should add the engine information that it has used to create a project.
> This would allow us to share Cordova CLI projects without the platforms
> directory and CLI to regenerate them
> Also it would help IDEs and tools work with CLI generated proects.
> As a note phonegap build adds a lib[1] object with version and uri to the
> fetch the engine. Although the approach is correct the information on the
> Cordova version should allow git URIs in addition to packaged ones.
> [1]
> {"lib":{"www":{"id":"phonegap","version":"3.0.0","uri":"https://github.com/phonegap/phonegap-app-hello-world/archive/3.0.0.tar.gz"}},"id":"AAA","name":"HelloWorld"}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4153) Add ability to select default app template at "cordova create" time
[ https://issues.apache.org/jira/browse/CB-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814333#comment-13814333 ] Braden Shepherdson commented on CB-4153: Didn't this get implemented? > Add ability to select default app template at "cordova create" time > --- > > Key: CB-4153 > URL: https://issues.apache.org/jira/browse/CB-4153 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 >Reporter: Michal Mocny >Assignee: Ian Clelland > > Proposal, Implement src flag to cordova create: > cordova create --src=... > Where src is: > * a valid path to a web app > * from a set of special values, perhaps including: > - default > - blank > - spec > - easteregg -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-2980) Add a ./cordova/lib/install-emulator project-level helper script
[
https://issues.apache.org/jira/browse/CB-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-2980.
Resolution: Fixed
All subtasks are complete.
> Add a ./cordova/lib/install-emulator project-level helper script
>
>
> Key: CB-2980
> URL: https://issues.apache.org/jira/browse/CB-2980
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI
>Reporter: Filip Maj
>Assignee: Lorin Beer
> Fix For: 3.2.0
>
>
> {code}
> install-emulator [--target=id]
> {code}
> Installs a build of the app to an available emulator.
> If {{--target}} is specified, attempts to install the app to the emulator
> identified by {{id}}. If the attempt fails, the script will error out with an
> appropriate error message and exit with code 2.
> If no {{--target}} is specified, follows this multi-device flow:
> # Are there any actual emulators available, i.e. started/running? (use
> {{list-started-emulators}} [CB-2964] to determine this). If so, target the
> first one, otherwise continue.
> # Are there any emulator images available to start? (use
> {{list-emulator-images}} [CB-2947] to determine this). If so, call
> {{start-emulator }} [TODO: issue ref] of the first available image, wait
> for it to become ready, then target it. If no, continue.
> # Print an error message and exit with code 2.
> If the application is not compiled/built yet, the script will error out with
> an appropriate error message and exit with code 2.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5220) "An error occurred" is missing an "A" ...
[
https://issues.apache.org/jira/browse/CB-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5220.
Resolution: Fixed
> "An error occurred" is missing an "A" ...
> -
>
> Key: CB-5220
> URL: https://issues.apache.org/jira/browse/CB-5220
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.1.0
>Reporter: Josh Soref
>
> ./cordova-cli/src/run.js:d.reject(new Error('n error occurred
> while running the ' + platform + ' project.' + errors));
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5279) Cordova - can't add android platform - package name is handled incorrectly ("dots" are replaced by "undefined")
[
https://issues.apache.org/jira/browse/CB-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814329#comment-13814329
]
Braden Shepherdson commented on CB-5279:
What version of Node are you running? Path.sep should be defined on all
platforms since 0.8. We only support Node 0.10, and it's definitely defined
there. Unless you're on some obscure platform Node doesn't know the separator
for?
> Cordova - can't add android platform - package name is handled incorrectly
> ("dots" are replaced by "undefined")
> ---
>
> Key: CB-5279
> URL: https://issues.apache.org/jira/browse/CB-5279
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CLI
>Affects Versions: 3.1.0
> Environment: $ uname -a
> Linux HP-Pro 3.2.0-39-generic-pae #62-Ubuntu SMP Wed Feb 27 22:25:11 UTC 2013
> i686 athlon i386 GNU/Linux
>Reporter: Giacomo Lombardello
>Priority: Blocker
>
> I'm new to Cordova and I'm trying to add android platform to my app, but it
> fails:
> {quote}
> $ cordova create myapp com.example.asd myapp
> Creating a new cordova project with name "myapp" and id "com.example.asd"
> at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
> $ cd myapp
> $ cordova platform add android
> Checking Android requirements...
> Creating android project...
> Preparing android project
> \{ [Error: ENOENT, no such file or directory
> '/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
> errno: 34,
> code: 'ENOENT',
> path:
> '/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
> syscall: 'readdir' \}
> {quote}
> It tries to reach an invalid path.
> I tried to investigate the issue and I found out that in src directory
> package name is handled incorrectly:
> {quote}
> $ ls platforms/android/src
> comundefinedexampleundefinedasd
> {quote}
> As you can see dots (".") are replaced by "undefined".
> By the way simply renaming the directory didn't solve the issue.
> Strangely cordova successfully handles package-name in other places:
> {quote}
> $ grep -ri com.example.asd .
> ./www/config.xml: xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
> ./platforms/android/res/xml/config.xml: version="0.0.1" xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
> ./platforms/android/AndroidManifest.xml: android:hardwareAccelerated="true" android:versionCode="1"
> android:versionName="0.0.1" android:windowSoftInputMode="adjustPan"
> package="com.example.asd"
> xmlns:android="http://schemas.android.com/apk/res/android";>
> ./platforms/android/assets/www/config.xml: id="com.example.asd" version="0.0.1" xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
>
> ./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
> com.example.asd;
> ./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
> {quote}
> My cordova version is
> {quote}
> $ cordova --v
> 3.1.0-0.2.0
> {quote}
> This issue affects "non-cli" Cordova either (I tried to make it work in
> eclipse).
> Thanks in advance for your help.
> EDIT:
> I'm replying to myself because I've edited manually sources and I think I
> removed the bug.
> line 128, ~/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js
> {quote}
> var package_as_path = package_name.replace(/\./g, path.sep);
> {quote}
> path.sep is undefined. I just replaced it with path sep of my os
> {quote}
> var package_as_path = package_name.replace(/\./g, '/');
> {quote}
> It seems to work normally now.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5143) CLI cordova prepare fails to copy the common files to android platform
[
https://issues.apache.org/jira/browse/CB-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5143.
Resolution: Fixed
Assignee: Braden Shepherdson (was: Lorin Beer)
> CLI cordova prepare fails to copy the common files to android platform
> --
>
> Key: CB-5143
> URL: https://issues.apache.org/jira/browse/CB-5143
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CLI
>Affects Versions: 3.1.0
> Environment: Windows
>Reporter: Peter
>Assignee: Braden Shepherdson
>Priority: Blocker
>
> I had created a CLI project, and then used CLI to add the android platform
> and add many plugins, etc.
> Then I used *cordova prepare* to copy my "common" www files to the android
> platform folders. This step worked OK for the simple _HelloWorld_ example
> from the CLI online guide, but for my full CLI project the prepare did not
> copy anything. The prepare processed the plugins OK, but nothing copied, and
> there was no error or any other indication what went wrong. (The -d debug
> flag did not help much either)
> Eventually, after consuming a lot of coffee the problem was isolated to a
> file called _android_parser.js_ which executes during the cordova prepare
> processing.
> This code...
> {code}
> var orig_java_class = fs.readdirSync(orig_pkgDir).filter(function(f) {return
> f.indexOf('.svn') == -1;})[0];
> {code}
> is apparently assuming that the main app java class is the _only_ (or
> _first_?) file found in the package directory. But this assumption is
> incorrect for my project (e.g. there are other sub-packages which were found
> ahead of the .java file) and so the script was failing shortly after this
> line of code, resulting in no copy... :(
> For example, my project structure resembles
> {code}
> src
> \-- com
> \-- fujitsu
> \-- mypkg
> \-- apkg1
> \-- bpkg2
> MyApp.java
> \-- zpkg3
> {code}
> To get arround this issue I am currently using using a hacky workaround -
> renaming the app java file with a prefix "AAA_" so that at least the zero
> offset can find it OK.
> {code}
> src
> \-- com
> \-- fujitsu
> \-- mypkg
> AAA_MyApp.java
> \-- apkg1
> \-- bpkg2
> \-- zpkg3
> {code}
> With this hack in place the cordova prepare copies the common files as
> expected.
> BTW - In fact I don't even use this file at all because my
> _AndroidManifest.xml_ is manually configured to launch a completely different
> main activity. But I have to leave this dummy AAA_MyApp.java file lying
> around just so the CLI cordova prepare will behave properly. If not for this
> issue then I would just delete it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5143) CLI cordova prepare fails to copy the common files to android platform
[
https://issues.apache.org/jira/browse/CB-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814323#comment-13814323
]
ASF subversion and git services commented on CB-5143:
-
Commit 5e68dff635e7dbe243672be67ca401d5ff8574a3 in branch refs/heads/master
from [~shepheb]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=5e68dff ]
[CB-5143] Locate the actual Android app .java file much more carefully.
> CLI cordova prepare fails to copy the common files to android platform
> --
>
> Key: CB-5143
> URL: https://issues.apache.org/jira/browse/CB-5143
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CLI
>Affects Versions: 3.1.0
> Environment: Windows
>Reporter: Peter
>Assignee: Lorin Beer
>Priority: Blocker
>
> I had created a CLI project, and then used CLI to add the android platform
> and add many plugins, etc.
> Then I used *cordova prepare* to copy my "common" www files to the android
> platform folders. This step worked OK for the simple _HelloWorld_ example
> from the CLI online guide, but for my full CLI project the prepare did not
> copy anything. The prepare processed the plugins OK, but nothing copied, and
> there was no error or any other indication what went wrong. (The -d debug
> flag did not help much either)
> Eventually, after consuming a lot of coffee the problem was isolated to a
> file called _android_parser.js_ which executes during the cordova prepare
> processing.
> This code...
> {code}
> var orig_java_class = fs.readdirSync(orig_pkgDir).filter(function(f) {return
> f.indexOf('.svn') == -1;})[0];
> {code}
> is apparently assuming that the main app java class is the _only_ (or
> _first_?) file found in the package directory. But this assumption is
> incorrect for my project (e.g. there are other sub-packages which were found
> ahead of the .java file) and so the script was failing shortly after this
> line of code, resulting in no copy... :(
> For example, my project structure resembles
> {code}
> src
> \-- com
> \-- fujitsu
> \-- mypkg
> \-- apkg1
> \-- bpkg2
> MyApp.java
> \-- zpkg3
> {code}
> To get arround this issue I am currently using using a hacky workaround -
> renaming the app java file with a prefix "AAA_" so that at least the zero
> offset can find it OK.
> {code}
> src
> \-- com
> \-- fujitsu
> \-- mypkg
> AAA_MyApp.java
> \-- apkg1
> \-- bpkg2
> \-- zpkg3
> {code}
> With this hack in place the cordova prepare copies the common files as
> expected.
> BTW - In fact I don't even use this file at all because my
> _AndroidManifest.xml_ is manually configured to launch a completely different
> main activity. But I have to leave this dummy AAA_MyApp.java file lying
> around just so the CLI cordova prepare will behave properly. If not for this
> issue then I would just delete it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Closed] (CB-5282) Platform dependencies fail to fetch via registry
[ https://issues.apache.org/jira/browse/CB-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins closed CB-5282. - Resolution: Invalid Issue in plugin.xml further down the dependency chain > Platform dependencies fail to fetch via registry > > > Key: CB-5282 > URL: https://issues.apache.org/jira/browse/CB-5282 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.1.0 >Reporter: Bryan Higgins > > If a dependency is defined within the platform tag, it is not fetched from > the registry. Error message states it must be in a git repo. > ci002088787:plugin3 bryan$ cordova plugin add com.blackberry.connection > Fetching plugin from "com.blackberry.connection"... > Starting installation of "com.blackberry.connection" for blackberry10 > Fetching plugin from "com.blackberry.jpps"... > Starting installation of "com.blackberry.jpps" for blackberry10 > [Error: Error: Plugin com.blackberry.jpps is not in git repository. All > plugins must be in a git repository.] -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5284) wrong version on master of cordova-android
[ https://issues.apache.org/jira/browse/CB-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard resolved CB-5284. --- Resolution: Fixed > wrong version on master of cordova-android > -- > > Key: CB-5284 > URL: https://issues.apache.org/jira/browse/CB-5284 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: Master > > > I think when coho was used to create the 2.9 branch, it went a bit out of > bounds and updated the "version" on master to be 2.10.0. > See this commit: > https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=937056fcaf078c67b93d9b5b0c04c3b6902b11ef > Is this the first time we've used coho for a maintenance branch? > I'll fix the versions in cordova-android master back to 3.2.0-dev. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5285) using coho on a maintenance branch had bad effect on master
Marcel Kinard created CB-5285: - Summary: using coho on a maintenance branch had bad effect on master Key: CB-5285 URL: https://issues.apache.org/jira/browse/CB-5285 Project: Apache Cordova Issue Type: Bug Components: Coho Reporter: Marcel Kinard Per CB-5284, it appears that when coho was used to update the hardcoded versions when creating 2.9.1 on the 2.9.x branch, it updated the hardcoded versions on master to be "2.10.0-dev". This is likely the first time we've tried to use coho on a maintenance branch. This behavior should be corrected before the next time we create another maintenance release (assuming there will there be a next time) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5284) wrong version on master of cordova-android
[ https://issues.apache.org/jira/browse/CB-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814191#comment-13814191 ] ASF subversion and git services commented on CB-5284: - Commit 4e1156e0835d87e277ab33df6d6c9dd2525bb09e in branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=4e1156e ] CB-5284 Fixing the version from coho Fixing the hardcoded versions, it got auto-incremented by accident. > wrong version on master of cordova-android > -- > > Key: CB-5284 > URL: https://issues.apache.org/jira/browse/CB-5284 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: Master > > > I think when coho was used to create the 2.9 branch, it went a bit out of > bounds and updated the "version" on master to be 2.10.0. > See this commit: > https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=937056fcaf078c67b93d9b5b0c04c3b6902b11ef > Is this the first time we've used coho for a maintenance branch? > I'll fix the versions in cordova-android master back to 3.2.0-dev. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5284) wrong version on master of cordova-android
[ https://issues.apache.org/jira/browse/CB-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814193#comment-13814193 ] Marcel Kinard commented on CB-5284: --- Looks like Joe already got the VERSION file in this commit: 1d6e1d416b02292856ca46936c8be2d8ea3c0191 > wrong version on master of cordova-android > -- > > Key: CB-5284 > URL: https://issues.apache.org/jira/browse/CB-5284 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: Master > > > I think when coho was used to create the 2.9 branch, it went a bit out of > bounds and updated the "version" on master to be 2.10.0. > See this commit: > https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=937056fcaf078c67b93d9b5b0c04c3b6902b11ef > Is this the first time we've used coho for a maintenance branch? > I'll fix the versions in cordova-android master back to 3.2.0-dev. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5284) wrong version on master of cordova-android
Marcel Kinard created CB-5284: - Summary: wrong version on master of cordova-android Key: CB-5284 URL: https://issues.apache.org/jira/browse/CB-5284 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: Master Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: Master I think when coho was used to create the 2.9 branch, it went a bit out of bounds and updated the "version" on master to be 2.10.0. See this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=commit;h=937056fcaf078c67b93d9b5b0c04c3b6902b11ef Is this the first time we've used coho for a maintenance branch? I'll fix the versions in cordova-android master back to 3.2.0-dev. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814068#comment-13814068
]
Mike Sierra commented on CB-5122:
-
FYI, [~mrbillau], so far I see the #1 use case for the shell-tool workflow is
when mixing WebViews with native components, applicable only to Android & iOS.
No decision; it's simply not possible with the CLI. But I want the Development
Guides to be very clear about any other marginal advantages, e.g., any syntax
options not reflected in CLI, or any advantages to perhaps having the SDK open
while running commands. Not clear on what these details might be for each
platform.
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814064#comment-13814064
]
Mike Sierra edited comment on CB-5122 at 11/5/13 5:40 PM:
--
Whoops [~mrbillau], didn't realize you had conflicting changes in various
"Platform Guides." Seems confined to Android. Making other comments inline on
your 5122 branch, mostly picayune
was (Author: sierra):
Whoops, didn't realize you had conflicting changes in various "Platform
Guides." Seems confined to Android. Making other comments inline on your 5122
branch, mostly picayune
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814064#comment-13814064
]
Mike Sierra edited comment on CB-5122 at 11/5/13 5:37 PM:
--
Whoops, didn't realize you had conflicting changes in various "Platform
Guides." Seems confined to Android. Making other comments inline on your 5122
branch, mostly picayune
was (Author: sierra):
Whoops, didn't realize you had conflicting changes in various "Platform
Guides." Seems confined to Android.
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814064#comment-13814064
]
Mike Sierra commented on CB-5122:
-
Whoops, didn't realize you had conflicting changes in various "Platform
Guides."
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814064#comment-13814064
]
Mike Sierra edited comment on CB-5122 at 11/5/13 5:36 PM:
--
Whoops, didn't realize you had conflicting changes in various "Platform
Guides." Seems confined to Android.
was (Author: sierra):
Whoops, didn't realize you had conflicting changes in various "Platform
Guides."
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5283) Cordova serve "server running" message should be more descriptive
James Keshavarzi created CB-5283: Summary: Cordova serve "server running" message should be more descriptive Key: CB-5283 URL: https://issues.apache.org/jira/browse/CB-5283 Project: Apache Cordova Issue Type: Improvement Components: CLI Reporter: James Keshavarzi Priority: Minor The current message displayed from cordova serve when the server is running is a bit confusing to some users. Suggested message below. Current message: Static file server running at => http://0.0.0.0:8000/ CTRL + C to shutdown Suggested message: Static file server running on port 8000 (i.e http://localhost:8000) CTRL + C to shutdown -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5122) Document supported workflows
[
https://issues.apache.org/jira/browse/CB-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814033#comment-13814033
]
Mike Sierra commented on CB-5122:
-
I'm currently reworking boilerplate exoskeleton text for platform
"Installation" and "Development" guides. See progress here in pull req #149:
https://github.com/apache/cordova-docs/pull/149/files. (Sorry for the "your"
global in this branch; scroll down to "/platforms/".) I may need follow-up help
fleshing out "Development" guides to reflect any marginal advantages of
shell-tool approach. Thx.
> Document supported workflows
>
>
> Key: CB-5122
> URL: https://issues.apache.org/jira/browse/CB-5122
> Project: Apache Cordova
> Issue Type: Bug
> Components: Docs
>Affects Versions: 3.1.0
>Reporter: Mike Billau
>Assignee: Mike Sierra
>
> Based on the recent discussion here [1]we should document the two different
> supported Cordova workflows: using the CLI, and using plugman and bin
> scripts.
> Some of this documentation already exists but needs to be clarified and
> improved:
> {{Overview guide --> "Development Paths" section}}. This talks about getting
> started with the CLI and then mentions that you can switch to the
> platform-specific SDK tools. This section should be rewritten to make it
> clear that there are two distinct workflows, and that both are okay and
> supported. It could list out some pros and cons of each workflow (I'm sure we
> won't have any trouble finding those ;)). It should be prescriptive in that
> users should be following one of the two workflows, but it shouldn't make any
> statements about which is better.
> {{"The Command-line Interface" guide}} --> The "CLI workflow" guide. It
> generally looks complete except for some missing functionality that is
> documented in the CLI's README.md file (tests, hooks, some commands (serve),
> some merges info).
> {{Platform Guides --> (Platform) --> (Platform) Command-line tools}} --> Each
> platform has a "Command-line tools" doc that explains all of the command line
> tools for that project and how to use them. We need to go through these
> guides and verify that they are up to date and include all of the lower level
> command line tools and scripts. It should read like a tutorial in the same
> way that the Command-line Interface guide does.
> {{"Using Plugman to Manage Plugins"}} First, this guide needs to get exposed;
> I can't find any way to get to this guide from the docs and even had to ask a
> user how she managed to find it (a link from Plugman's readme!). This guide
> needs to be expanded quite a bit; we can probably fold most/all of Plugman's
> README.md file into this guide since it will be platform agnostic.
> I think those are the only pieces in the docs that need to be changed.
> [1] http://callback.markmail.org/thread/5nr7dgkquse4gdkl
> [2]
> http://cordova.apache.org/docs/en/edge/guide_overview_index.md.html#Overview
> [3] http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5282) Platform dependencies fail to fetch via registry
Bryan Higgins created CB-5282: - Summary: Platform dependencies fail to fetch via registry Key: CB-5282 URL: https://issues.apache.org/jira/browse/CB-5282 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 3.1.0 Reporter: Bryan Higgins If a dependency is defined within the platform tag, it is not fetched from the registry. Error message states it must be in a git repo. ci002088787:plugin3 bryan$ cordova plugin add com.blackberry.connection Fetching plugin from "com.blackberry.connection"... Starting installation of "com.blackberry.connection" for blackberry10 Fetching plugin from "com.blackberry.jpps"... Starting installation of "com.blackberry.jpps" for blackberry10 [Error: Error: Plugin com.blackberry.jpps is not in git repository. All plugins must be in a git repository.] -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5281) [BlackBerry10] Implement plugin aliasing
[ https://issues.apache.org/jira/browse/CB-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814023#comment-13814023 ] Jeffrey Heifetz commented on CB-5281: - So the service specified in exec actually maps to the folder where the plugin is installed. The plugin installation folder is determined by either a target-id attribute on the source-file element or the plugin id. > [BlackBerry10] Implement plugin aliasing > > > Key: CB-5281 > URL: https://issues.apache.org/jira/browse/CB-5281 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.0.0, 3.1.0 >Reporter: Bryan Higgins > > BB10 plugins use plugin id for both sides of the exec bridge. It should be > possible to override this using the feature element in config.xml -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4531) BlackBerry10 bin/check_reqs scripts (sh, bat + js) should exit with code 2 if an error occurs
[ https://issues.apache.org/jira/browse/CB-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814024#comment-13814024 ] ASF subversion and git services commented on CB-4531: - Commit 4dcdb991179c419765f5af5ec0c911fc29ff5fb4 in branch refs/heads/master from [~jsoref] [ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=4dcdb99 ] CB-4531 bin/check_reqs scripts exit with code 2 on error - Return ERROR_VALUE/NOTIMPLEMENTED_VALUE - Restore number path for symmetry with install-emulator, install-device, build - Refactor exit_handler into utils Reviewed by James Keshavarzi Tested by Jenny Gee > BlackBerry10 bin/check_reqs scripts (sh, bat + js) should exit with code 2 if > an error occurs > - > > Key: CB-4531 > URL: https://issues.apache.org/jira/browse/CB-4531 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.0.0 >Reporter: Filip Maj >Assignee: Bryan Higgins >Priority: Minor > Fix For: 3.2.0 > > > As per title! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-2086) Invoke default android file picker for html file input
[ https://issues.apache.org/jira/browse/CB-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814009#comment-13814009 ] julio cesar commented on CB-2086: - It doesn't work if you use it in a cordova embedded webview. Tested on phonegap 2.9 and 3.1. In both the file choser appears, but when you select a file it returns to the main view, but the cordova webview gets blocked and there is no log message with the file info. > Invoke default android file picker for html file input > -- > > Key: CB-2086 > URL: https://issues.apache.org/jira/browse/CB-2086 > Project: Apache Cordova > Issue Type: Wish > Components: Android >Affects Versions: 2.2.0 >Reporter: Mark Dineen >Assignee: Joe Bowser > Fix For: 2.4.0 > > > PhoneGap build currently doesn't invoke the Android file picker when a > input[type=file] is clicked. This behaviour can (apparently) be overridden > with some code changes in Cordova itself. > http://tmkmobile.wordpress.com/2012/0... > http://stackoverflow.com/questions/59... > Can this be introduced? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5183) WP7/8 lib path is not correctly resolved by CLI
[
https://issues.apache.org/jira/browse/CB-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813988#comment-13813988
]
Sergey Grebnov commented on CB-5183:
Fixed by the following PR
https://github.com/apache/cordova-cli/pull/68
> WP7/8 lib path is not correctly resolved by CLI
> ---
>
> Key: CB-5183
> URL: https://issues.apache.org/jira/browse/CB-5183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Sergey Grebnov
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> Steps to reproduce
> 1. Install latest cordova-cli from git repo
> 2. Create new project App using 'cordova create App' CLI command
> 3. Update app/.cordova/config.json to point to custom cordova-wp8 repo
> For example
> { "id":"org.apache.mobilespec", "name":"mobilespec", "lib": { "wp8": {
> "uri": "c:\\..\\cordova-wp8", "version": "3.1.0", "id":
> "cordova-wp8-master"} }}
> 4. Run 'cordova platform add wp8' commands
> Expected: command succeeded.
> Actually: command failed with the message below
> Error: Error while checking requirements:
> '"c:\..\cordova-wp8\bin\check_reqs"' is not recognized as an internal or
> external command,
> operable program or batch file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (CB-5183) WP7/8 lib path is not correctly resolved by CLI
[
https://issues.apache.org/jira/browse/CB-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813943#comment-13813943
]
Sergey Grebnov edited comment on CB-5183 at 11/5/13 2:37 PM:
-
Same issue exists for Windows8
was (Author: sgrebnov):
I see that there is cordova-cli/spec folder that have some related logic
modified. Asked question to dev list...
> WP7/8 lib path is not correctly resolved by CLI
> ---
>
> Key: CB-5183
> URL: https://issues.apache.org/jira/browse/CB-5183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Sergey Grebnov
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> Steps to reproduce
> 1. Install latest cordova-cli from git repo
> 2. Create new project App using 'cordova create App' CLI command
> 3. Update app/.cordova/config.json to point to custom cordova-wp8 repo
> For example
> { "id":"org.apache.mobilespec", "name":"mobilespec", "lib": { "wp8": {
> "uri": "c:\\..\\cordova-wp8", "version": "3.1.0", "id":
> "cordova-wp8-master"} }}
> 4. Run 'cordova platform add wp8' commands
> Expected: command succeeded.
> Actually: command failed with the message below
> Error: Error while checking requirements:
> '"c:\..\cordova-wp8\bin\check_reqs"' is not recognized as an internal or
> external command,
> operable program or batch file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5280) "cordova serve platformname 9000" as per help does not seem to serve platformname on port 9000
[ https://issues.apache.org/jira/browse/CB-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JennyGee updated CB-5280: - Summary: "cordova serve platformname 9000" as per help does not seem to serve platformname on port 9000 (was: "cordova serve" doesn't recognize the specified port) > "cordova serve platformname 9000" as per help does not seem to serve > platformname on port 9000 > -- > > Key: CB-5280 > URL: https://issues.apache.org/jira/browse/CB-5280 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: JennyGee >Priority: Minor > > When executing the following: > "cordova serve blackberry10 9901" > The webserver doesn't actually run on port 9901 but rather on the default > port "8000". So you can only access your app via > http://0.0.0.0:8000/blackberry10/www/index.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5281) [BlackBerry10] Implement plugin aliasing
Bryan Higgins created CB-5281: - Summary: [BlackBerry10] Implement plugin aliasing Key: CB-5281 URL: https://issues.apache.org/jira/browse/CB-5281 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0, 3.0.0 Reporter: Bryan Higgins BB10 plugins use plugin id for both sides of the exec bridge. It should be possible to override this using the feature element in config.xml -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5280) "cordova serve platformname 9000" as per help does not seem to serve platformname on port 9000
[ https://issues.apache.org/jira/browse/CB-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JennyGee updated CB-5280: - Description: When executing the following: "cordova serve blackberry10 9901" The webserver doesn't actually run on port 9901 but rather on the default port "8000". So you can only access your app via http://0.0.0.0:8000/blackberry10/www/index.html The following: "cordova serve 9901" allows one to access http://0.0.0.0:9901/blackberry10/www/index.html It seems like this is mostly a bug in the documentation (`cordova help |grep -C1 8000`) was: When executing the following: "cordova serve blackberry10 9901" The webserver doesn't actually run on port 9901 but rather on the default port "8000". So you can only access your app via http://0.0.0.0:8000/blackberry10/www/index.html > "cordova serve platformname 9000" as per help does not seem to serve > platformname on port 9000 > -- > > Key: CB-5280 > URL: https://issues.apache.org/jira/browse/CB-5280 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: JennyGee >Priority: Minor > > When executing the following: > "cordova serve blackberry10 9901" > The webserver doesn't actually run on port 9901 but rather on the default > port "8000". So you can only access your app via > http://0.0.0.0:8000/blackberry10/www/index.html > The following: > "cordova serve 9901" > allows one to access http://0.0.0.0:9901/blackberry10/www/index.html > It seems like this is mostly a bug in the documentation (`cordova help |grep > -C1 8000`) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5183) WP7/8 lib path is not correctly resolved by CLI
[
https://issues.apache.org/jira/browse/CB-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813943#comment-13813943
]
Sergey Grebnov commented on CB-5183:
I see that there is cordova-cli/spec folder that have some related logic
modified. Asked question to dev list...
> WP7/8 lib path is not correctly resolved by CLI
> ---
>
> Key: CB-5183
> URL: https://issues.apache.org/jira/browse/CB-5183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Sergey Grebnov
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> Steps to reproduce
> 1. Install latest cordova-cli from git repo
> 2. Create new project App using 'cordova create App' CLI command
> 3. Update app/.cordova/config.json to point to custom cordova-wp8 repo
> For example
> { "id":"org.apache.mobilespec", "name":"mobilespec", "lib": { "wp8": {
> "uri": "c:\\..\\cordova-wp8", "version": "3.1.0", "id":
> "cordova-wp8-master"} }}
> 4. Run 'cordova platform add wp8' commands
> Expected: command succeeded.
> Actually: command failed with the message below
> Error: Error while checking requirements:
> '"c:\..\cordova-wp8\bin\check_reqs"' is not recognized as an internal or
> external command,
> operable program or batch file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5280) "cordova serve" doesn't recognize the specified port
JennyGee created CB-5280: Summary: "cordova serve" doesn't recognize the specified port Key: CB-5280 URL: https://issues.apache.org/jira/browse/CB-5280 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: JennyGee Priority: Minor When executing the following: "cordova serve blackberry10 9901" The webserver doesn't actually run on port 9901 but rather on the default port "8000". So you can only access your app via http://0.0.0.0:8000/blackberry10/www/index.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5183) WP7/8 lib path is not correctly resolved by CLI
[
https://issues.apache.org/jira/browse/CB-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Grebnov updated CB-5183:
---
Summary: WP7/8 lib path is not correctly resolved by CLI (was: WP7/8
custom_path is not correctly resolved by CLI)
> WP7/8 lib path is not correctly resolved by CLI
> ---
>
> Key: CB-5183
> URL: https://issues.apache.org/jira/browse/CB-5183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Sergey Grebnov
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> Steps to reproduce
> 1. Install latest cordova-cli from git repo
> 2. Create new project App using 'cordova create App' CLI command
> 3. Update app/.cordova/config.json to point to custom cordova-wp8 repo
> For example
> { "id":"org.apache.mobilespec", "name":"mobilespec", "lib": { "wp8": {
> "uri": "c:\\..\\cordova-wp8", "version": "3.1.0", "id":
> "cordova-wp8-master"} }}
> 4. Run 'cordova platform add wp8' commands
> Expected: command succeeded.
> Actually: command failed with the message below
> Error: Error while checking requirements:
> '"c:\..\cordova-wp8\bin\check_reqs"' is not recognized as an internal or
> external command,
> operable program or batch file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5183) WP7/8 lib path is not correctly resolved by CLI
[
https://issues.apache.org/jira/browse/CB-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813934#comment-13813934
]
Sergey Grebnov commented on CB-5183:
Don's error is caused by the changes added in the following commit
https://github.com/apache/cordova-cli/commit/d75c0585c88ee9283db400f0c946027bd9d6e1ea
Renamed issue to be more general
WP7/8 custom_path is not correctly resolved by CLI -> WP7/8 lib path is not
correctly resolved by CLI
> WP7/8 lib path is not correctly resolved by CLI
> ---
>
> Key: CB-5183
> URL: https://issues.apache.org/jira/browse/CB-5183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Sergey Grebnov
>Assignee: Jesse MacFadyen
>Priority: Minor
>
> Steps to reproduce
> 1. Install latest cordova-cli from git repo
> 2. Create new project App using 'cordova create App' CLI command
> 3. Update app/.cordova/config.json to point to custom cordova-wp8 repo
> For example
> { "id":"org.apache.mobilespec", "name":"mobilespec", "lib": { "wp8": {
> "uri": "c:\\..\\cordova-wp8", "version": "3.1.0", "id":
> "cordova-wp8-master"} }}
> 4. Run 'cordova platform add wp8' commands
> Expected: command succeeded.
> Actually: command failed with the message below
> Error: Error while checking requirements:
> '"c:\..\cordova-wp8\bin\check_reqs"' is not recognized as an internal or
> external command,
> operable program or batch file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5274) [Blackberry10] cordova run does not prompt you for a device password
[ https://issues.apache.org/jira/browse/CB-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins updated CB-5274: -- Component/s: BlackBerry Summary: [Blackberry10] cordova run does not prompt you for a device password (was: cordova run does not prompt you for a device password) > [Blackberry10] cordova run does not prompt you for a device password > > > Key: CB-5274 > URL: https://issues.apache.org/jira/browse/CB-5274 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Reporter: JennyGee >Priority: Minor > > Ensure that a device is attached to your machine before executing. > ci003068684:Some Directory jgee$ cordova run > Generating config.xml from defaults for platform "blackberry10" > Preparing blackberry10 project > Running app on platform "blackberry10" via command > "/Users/jgee/RippleSites/cordovaTest/Some > Directory/platforms/blackberry10/cordova/run" --device > [Error: An error occurred while running the blackberry10 project.] > If you check verbose it'll tell you that you're missing the password. But > before it fails, it should at least ask you for the password -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5279) Cordova - can't add android platform - package name is handled incorrectly ("dots" are replaced by "undefined")
[
https://issues.apache.org/jira/browse/CB-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Lombardello updated CB-5279:
Description:
I'm new to Cordova and I'm trying to add android platform to my app, but it
fails:
{quote}
$ cordova create myapp com.example.asd myapp
Creating a new cordova project with name "myapp" and id "com.example.asd"
at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
$ cd myapp
$ cordova platform add android
Checking Android requirements...
Creating android project...
Preparing android project
\{ [Error: ENOENT, no such file or directory
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
errno: 34,
code: 'ENOENT',
path:
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
syscall: 'readdir' \}
{quote}
It tries to reach an invalid path.
I tried to investigate the issue and I found out that in src directory package
name is handled incorrectly:
{quote}
$ ls platforms/android/src
comundefinedexampleundefinedasd
{quote}
As you can see dots (".") are replaced by "undefined".
By the way simply renaming the directory didn't solve the issue.
Strangely cordova successfully handles package-name in other places:
{quote}
$ grep -ri com.example.asd .
./www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/res/xml/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/AndroidManifest.xml:http://schemas.android.com/apk/res/android";>
./platforms/android/assets/www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
com.example.asd;
./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
{quote}
My cordova version is
{quote}
$ cordova --v
3.1.0-0.2.0
{quote}
This issue affects "non-cli" Cordova either (I tried to make it work in
eclipse).
Thanks in advance for your help.
EDIT:
I'm replying to myself because I've edited manually sources and I think I
removed the bug.
line 128, ~/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js
var package_as_path = package_name.replace(/\./g, path.sep);
path.sep is undefined. I just replaced it with path sep of my os
var package_as_path = package_name.replace(/\./g, '/');
It seems to work normally now.
was:
I'm new to Cordova and I'm trying to add android platform to my app, but it
fails:
{quote}
$ cordova create myapp com.example.asd myapp
Creating a new cordova project with name "myapp" and id "com.example.asd"
at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
$ cd myapp
$ cordova platform add android
Checking Android requirements...
Creating android project...
Preparing android project
\{ [Error: ENOENT, no such file or directory
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
errno: 34,
code: 'ENOENT',
path:
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
syscall: 'readdir' \}
{quote}
It tries to reach an invalid path.
I tried to investigate the issue and I found out that in src directory package
name is handled incorrectly:
{quote}
$ ls platforms/android/src
comundefinedexampleundefinedasd
{quote}
As you can see dots (".") are replaced by "undefined".
By the way simply renaming the directory didn't solve the issue.
Strangely cordova successfully handles package-name in other places:
{quote}
$ grep -ri com.example.asd .
./www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/res/xml/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/AndroidManifest.xml:http://schemas.android.com/apk/res/android";>
./platforms/android/assets/www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
com.example.asd;
./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
{quote}
My cordova version is
{quote}
$ cordova --v
3.1.0-0.2.0
{quote}
This issue affects "non-cli" Cordova either (I tried to make it work in
eclipse).
Thanks in advance for your help.
> Cordova - can't add android platform - package name is handled incorrectly
> ("dots" are replaced by "undefined")
> ---
[jira] [Updated] (CB-5279) Cordova - can't add android platform - package name is handled incorrectly ("dots" are replaced by "undefined")
[
https://issues.apache.org/jira/browse/CB-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Lombardello updated CB-5279:
Description:
I'm new to Cordova and I'm trying to add android platform to my app, but it
fails:
{quote}
$ cordova create myapp com.example.asd myapp
Creating a new cordova project with name "myapp" and id "com.example.asd"
at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
$ cd myapp
$ cordova platform add android
Checking Android requirements...
Creating android project...
Preparing android project
\{ [Error: ENOENT, no such file or directory
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
errno: 34,
code: 'ENOENT',
path:
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
syscall: 'readdir' \}
{quote}
It tries to reach an invalid path.
I tried to investigate the issue and I found out that in src directory package
name is handled incorrectly:
{quote}
$ ls platforms/android/src
comundefinedexampleundefinedasd
{quote}
As you can see dots (".") are replaced by "undefined".
By the way simply renaming the directory didn't solve the issue.
Strangely cordova successfully handles package-name in other places:
{quote}
$ grep -ri com.example.asd .
./www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/res/xml/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/AndroidManifest.xml:http://schemas.android.com/apk/res/android";>
./platforms/android/assets/www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
com.example.asd;
./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
{quote}
My cordova version is
{quote}
$ cordova --v
3.1.0-0.2.0
{quote}
This issue affects "non-cli" Cordova either (I tried to make it work in
eclipse).
Thanks in advance for your help.
EDIT:
I'm replying to myself because I've edited manually sources and I think I
removed the bug.
line 128, ~/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js
{quote}
var package_as_path = package_name.replace(/\./g, path.sep);
{quote}
path.sep is undefined. I just replaced it with path sep of my os
{quote}
var package_as_path = package_name.replace(/\./g, '/');
{quote}
It seems to work normally now.
was:
I'm new to Cordova and I'm trying to add android platform to my app, but it
fails:
{quote}
$ cordova create myapp com.example.asd myapp
Creating a new cordova project with name "myapp" and id "com.example.asd"
at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
$ cd myapp
$ cordova platform add android
Checking Android requirements...
Creating android project...
Preparing android project
\{ [Error: ENOENT, no such file or directory
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
errno: 34,
code: 'ENOENT',
path:
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
syscall: 'readdir' \}
{quote}
It tries to reach an invalid path.
I tried to investigate the issue and I found out that in src directory package
name is handled incorrectly:
{quote}
$ ls platforms/android/src
comundefinedexampleundefinedasd
{quote}
As you can see dots (".") are replaced by "undefined".
By the way simply renaming the directory didn't solve the issue.
Strangely cordova successfully handles package-name in other places:
{quote}
$ grep -ri com.example.asd .
./www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/res/xml/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/AndroidManifest.xml:http://schemas.android.com/apk/res/android";>
./platforms/android/assets/www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
com.example.asd;
./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
{quote}
My cordova version is
{quote}
$ cordova --v
3.1.0-0.2.0
{quote}
This issue affects "non-cli" Cordova either (I tried to make it work in
eclipse).
Thanks in advance for your help.
EDIT:
I'm replying to myself because I've edited manually sources and I think I
removed the bug.
line 128, ~/.cordova/lib/android/cordova/3.1.0/bin/lib/create.js
var package_as_path = package
[jira] [Created] (CB-5279) Cordova - can't add android platform - package name is handled incorrectly ("dots" are replaced by "undefined")
Giacomo Lombardello created CB-5279:
---
Summary: Cordova - can't add android platform - package name is
handled incorrectly ("dots" are replaced by "undefined")
Key: CB-5279
URL: https://issues.apache.org/jira/browse/CB-5279
Project: Apache Cordova
Issue Type: Bug
Components: Android, CLI
Affects Versions: 3.1.0
Environment: $ uname -a
Linux HP-Pro 3.2.0-39-generic-pae #62-Ubuntu SMP Wed Feb 27 22:25:11 UTC 2013
i686 athlon i386 GNU/Linux
Reporter: Giacomo Lombardello
Priority: Blocker
I'm new to Cordova and I'm trying to add android platform to my app, but it
fails:
{quote}
$ cordova create myapp com.example.asd myapp
Creating a new cordova project with name "myapp" and id "com.example.asd"
at location "/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp"
$ cd myapp
$ cordova platform add android
Checking Android requirements...
Creating android project...
Preparing android project
\{ [Error: ENOENT, no such file or directory
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd']
errno: 34,
code: 'ENOENT',
path:
'/home/user/Scaricati/android/eclipse/alternativeworkspace/myapp/platforms/android/src/com/example/asd',
syscall: 'readdir' \}
{quote}
It tries to reach an invalid path.
I tried to investigate the issue and I found out that in src directory package
name is handled incorrectly:
{quote}
$ ls platforms/android/src
comundefinedexampleundefinedasd
{quote}
As you can see dots (".") are replaced by "undefined".
By the way simply renaming the directory didn't solve the issue.
Strangely cordova successfully handles package-name in other places:
{quote}
$ grep -ri com.example.asd .
./www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/res/xml/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/AndroidManifest.xml:http://schemas.android.com/apk/res/android";>
./platforms/android/assets/www/config.xml:http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
./platforms/android/src/comundefinedexampleundefinedasd/myapp.java:package
com.example.asd;
./.cordova/config.json:\{"id":"com.example.asd","name":"myapp"\}
{quote}
My cordova version is
{quote}
$ cordova --v
3.1.0-0.2.0
{quote}
This issue affects "non-cli" Cordova either (I tried to make it work in
eclipse).
Thanks in advance for your help.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5261) Missing pre_package event for WP8
[ https://issues.apache.org/jira/browse/CB-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick van den Brink resolved CB-5261. Resolution: Fixed Fix Version/s: 3.2.0 Fixed, see CB-5272 for details. > Missing pre_package event for WP8 > - > > Key: CB-5261 > URL: https://issues.apache.org/jira/browse/CB-5261 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.1.0 >Reporter: Dick van den Brink > Fix For: 3.2.0 > > > The WP8 parser is missing a pre_package event. It is in the WP7 project > parser. > Also the pre_package event doesn't work correctly on the WP7 project because > hooks are async. > Pullrequest: https://github.com/apache/cordova-cli/pull/43 -- This message was sent by Atlassian JIRA (v6.1#6144)
