[jira] [Commented] (CB-5783) Cordova/plugin_list - module.exports are always empty
[
https://issues.apache.org/jira/browse/CB-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874852#comment-13874852
]
Braden Shepherdson commented on CB-5783:
That is the expected behavior.
platforms/* are build artifacts, and generally should not be edited by hand.
The place to edit your code is in the top-level www/, and this is copied on
cordova prepare. I'm sorry you lost some work in the
platforms/android/assets/www directory.
The next version of the command-line tools release (currently having problems
because of npm failures) should include a patch that will make the top-level
www and config.xml appear in IDEs like Eclipse and Xcode, rather than the
platforms/android/assets/www, so that edits will be happening in the right
places. You'll still need to run cordova prepare after editing, though, at
least for now.
> Cordova/plugin_list - module.exports are always empty
> -
>
> Key: CB-5783
> URL: https://issues.apache.org/jira/browse/CB-5783
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 3.3.0
> Environment: Test the app in a desktop browser
>Reporter: Kevin Lucich
> Labels: cordova, plugin_list, plugins
> Fix For: 3.3.0
>
>
> When i tested the apps in desktop browser (version Cordova 3.0.0) i don't
> received any error. when i update Cordova i note that the file
> "cordova_plugins.js" has variable empty ("module.exports" is empty array).
> Before the update this file contained the list of installated plugins.
> Why is now empty?
> This problem causes the fact that I receive the error "navigator.connection
> is undefined"
> /
> Old Cordova - after installations a plugin
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [
> [...]
> {
> "file":
> "plugins/org.apache.cordova.network-information/www/network.js",
> "id": "org.apache.cordova.network-information.network",
> "clobbers": [
> "navigator.connection",
> "navigator.network.connection"
> ]
> },
> [...]
> ]
> });
> /
> Cordova 3.3.0
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [];
> module.exports.metadata =
> // TOP OF METADATA
> {}
> // BOTTOM OF METADATA
> });
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-5783) Cordova/plugin_list - module.exports are always empty
[
https://issues.apache.org/jira/browse/CB-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873525#comment-13873525
]
Braden Shepherdson commented on CB-5783:
All of which assets? Top-level www/? plugins/? Everything in platforms/android?
In platforms/android/assets/www/?
> Cordova/plugin_list - module.exports are always empty
> -
>
> Key: CB-5783
> URL: https://issues.apache.org/jira/browse/CB-5783
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 3.3.0
> Environment: Test the app in a desktop browser
>Reporter: Kevin Lucich
> Labels: cordova, plugin_list, plugins
> Fix For: 3.3.0
>
>
> When i tested the apps in desktop browser (version Cordova 3.0.0) i don't
> received any error. when i update Cordova i note that the file
> "cordova_plugins.js" has variable empty ("module.exports" is empty array).
> Before the update this file contained the list of installated plugins.
> Why is now empty?
> This problem causes the fact that I receive the error "navigator.connection
> is undefined"
> /
> Old Cordova - after installations a plugin
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [
> [...]
> {
> "file":
> "plugins/org.apache.cordova.network-information/www/network.js",
> "id": "org.apache.cordova.network-information.network",
> "clobbers": [
> "navigator.connection",
> "navigator.network.connection"
> ]
> },
> [...]
> ]
> });
> /
> Cordova 3.3.0
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [];
> module.exports.metadata =
> // TOP OF METADATA
> {}
> // BOTTOM OF METADATA
> });
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Closed] (CB-5381) Runtime plugin discovery on iOS
[ https://issues.apache.org/jira/browse/CB-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5381. -- Resolution: Won't Fix Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on iOS > --- > > Key: CB-5381 > URL: https://issues.apache.org/jira/browse/CB-5381 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Braden Shepherdson >Assignee: Braden Shepherdson > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CB-5379) Runtime discovery of installed plugins
[
https://issues.apache.org/jira/browse/CB-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5379.
Resolution: Won't Fix
Fix Version/s: (was: 3.4.0)
We're not actually going to make this change anymore. It's been partially
replaced with Javascript-side code as described above.
> Runtime discovery of installed plugins
> --
>
> Key: CB-5379
> URL: https://issues.apache.org/jira/browse/CB-5379
> Project: Apache Cordova
> Issue Type: New Feature
> Components: Android, BlackBerry, FirefoxOS, iOS, Windows 8, WP7, WP8
>Reporter: Braden Shepherdson
>Assignee: Braden Shepherdson
>
> We want Cordova apps to be able to query what plugins (and versions) are
> installed at runtime.
> Plugman is now injecting a tag of the kind:
> {code:xml}
>
>
>
>
> {code}
> into the platform's config.xml. Each platform should be parsing this and
> exposing it to native plugins ({{PluginManager.getPluginList()}}, or
> something like that) and exposing it to Javascript via the following {{exec}}
> call:
> {code:javascript}
> cordova.exec('CordovaPlugins', 'getPluginList', [], ...);
> {code}
> The format of the exec call's response is a JS object whose keys are plugin
> IDs and whose values are their versions.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Closed] (CB-5383) Runtime plugin discovery on WP7
[ https://issues.apache.org/jira/browse/CB-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5383. -- Resolution: Won't Fix Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on WP7 > --- > > Key: CB-5383 > URL: https://issues.apache.org/jira/browse/CB-5383 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP7 >Reporter: Braden Shepherdson >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CB-5384) Runtime plugin discovery on WP8
[ https://issues.apache.org/jira/browse/CB-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5384. -- Resolution: Fixed Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on WP8 > --- > > Key: CB-5384 > URL: https://issues.apache.org/jira/browse/CB-5384 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP8 >Reporter: Braden Shepherdson >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CB-5382) Runtime plugin discovery on BB10
[ https://issues.apache.org/jira/browse/CB-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5382. -- Resolution: Won't Fix Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on BB10 > > > Key: CB-5382 > URL: https://issues.apache.org/jira/browse/CB-5382 > Project: Apache Cordova > Issue Type: Sub-task > Components: BlackBerry >Reporter: Braden Shepherdson > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CB-5385) Runtime plugin discovery on Firefox
[ https://issues.apache.org/jira/browse/CB-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5385. -- Resolution: Fixed Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on Firefox > --- > > Key: CB-5385 > URL: https://issues.apache.org/jira/browse/CB-5385 > Project: Apache Cordova > Issue Type: Sub-task > Components: FirefoxOS >Reporter: Braden Shepherdson > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CB-5380) Runtime plugin discovery on Android
[ https://issues.apache.org/jira/browse/CB-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5380. -- Resolution: Won't Fix Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on Android > --- > > Key: CB-5380 > URL: https://issues.apache.org/jira/browse/CB-5380 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Braden Shepherdson >Assignee: Braden Shepherdson > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CB-5386) Runtime plugin discovery on Windows8
[ https://issues.apache.org/jira/browse/CB-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson closed CB-5386. -- Resolution: Won't Fix Fix Version/s: (was: 3.4.0) > Runtime plugin discovery on Windows8 > > > Key: CB-5386 > URL: https://issues.apache.org/jira/browse/CB-5386 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows 8 >Reporter: Braden Shepherdson >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5379) Runtime discovery of installed plugins
[
https://issues.apache.org/jira/browse/CB-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870996#comment-13870996
]
Braden Shepherdson commented on CB-5379:
This has been reverted. The plugin list now exists only on the Javascript side,
as cordova.require('cordova/plugin_list').metadata, which is a map of plugin
IDs to their versions.
I'm closing this bug, and the subtasks.
> Runtime discovery of installed plugins
> --
>
> Key: CB-5379
> URL: https://issues.apache.org/jira/browse/CB-5379
> Project: Apache Cordova
> Issue Type: New Feature
> Components: Android, BlackBerry, FirefoxOS, iOS, Windows 8, WP7, WP8
>Reporter: Braden Shepherdson
>Assignee: Braden Shepherdson
> Fix For: 3.4.0
>
>
> We want Cordova apps to be able to query what plugins (and versions) are
> installed at runtime.
> Plugman is now injecting a tag of the kind:
> {code:xml}
>
>
>
>
> {code}
> into the platform's config.xml. Each platform should be parsing this and
> exposing it to native plugins ({{PluginManager.getPluginList()}}, or
> something like that) and exposing it to Javascript via the following {{exec}}
> call:
> {code:javascript}
> cordova.exec('CordovaPlugins', 'getPluginList', [], ...);
> {code}
> The format of the exec call's response is a JS object whose keys are plugin
> IDs and whose values are their versions.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CB-5728) Files in merges must remain intact when removing platform
[ https://issues.apache.org/jira/browse/CB-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-5728. Resolution: Fixed Fix Version/s: 3.4.0 Assignee: Braden Shepherdson Merged the PR as 40d6b974844d5bf02ed370d313127bedfd23ea13. > Files in merges must remain intact when removing platform > - > > Key: CB-5728 > URL: https://issues.apache.org/jira/browse/CB-5728 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.2.0 >Reporter: Ivan Baktsheev >Assignee: Braden Shepherdson > Fix For: 3.4.0 > > > platform rm must not delete files in `merges` dir. > 1) this is completely unexpected and not documented in any way; > 2) lost some files because of this; project after `platform rm && platform > add` is broken because of empty merges dir. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5714) Android build fails when there is too much output
[
https://issues.apache.org/jira/browse/CB-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863252#comment-13863252
]
Braden Shepherdson commented on CB-5714:
Yes please, change this to use {{spawn()}}.
> Android build fails when there is too much output
> -
>
> Key: CB-5714
> URL: https://issues.apache.org/jira/browse/CB-5714
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Andrew Grieve
>Assignee: Andrew Grieve
> Fix For: 3.4.0
>
>
> Reported from pull request:
> https://github.com/apache/cordova-android/pull/90
> Probably even better fix would be to use child_process.spawn(), but
> increasing the buffer is a good quick-fix.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-5675) Can't get rid of Hello Cordova from config.xml
[ https://issues.apache.org/jira/browse/CB-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863052#comment-13863052 ] Braden Shepherdson commented on CB-5675: Making that change to SINGLETONS sounds good to me. Normally I'd ask that you send a pull request, but this change is simple enough that it's not worth the overhead. I'll make the change today. > Can't get rid of Hello Cordova from config.xml > - > > Key: CB-5675 > URL: https://issues.apache.org/jira/browse/CB-5675 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.2.0 > Environment: OSX/IOS >Reporter: Michael Stanford > Fix For: Master > > > config_parser.js merges your www/config.xml in on top of cordova/defaults.xml > to produce your platform//config.xml. > I don't like seeing "Hello Cordova" in there as the name of the project in > addition to the one that I gave it. Same with the description. I am concerned > that it confuses Xcode as well. > So I changed the SINGLETONS array in config_parser.merge_with() from: > ["content", "author"] > to: > ["content", "author","description","name"] > Which seems to have fixed my problem. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-5454) Plugin Mapping Issue
[ https://issues.apache.org/jira/browse/CB-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836925#comment-13836925 ] Braden Shepherdson commented on CB-5454: I can't reproduce this against master. To those who are having the issues: npm install the latest cordova-cli and try again. > Plugin Mapping Issue > > > Key: CB-5454 > URL: https://issues.apache.org/jira/browse/CB-5454 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, iOS, Plugins >Affects Versions: 3.1.0 > Environment: iOS >Reporter: Mike Hartington >Assignee: Braden Shepherdson > Labels: cli, config.xml,, cordova, cordova-cli > > Once I've removed a plugin, I'm unable to add any plugins back again. So from > the command line, > cordova plugin rm org.apache.cordova.device > cordova plugin add org.apache.cordova.device > Everything installs properly but once I go into Xcode and run the project, my > console puts out > 2013-11-20 14:59:28.301 ProductDemo[65497:a0b] CDVPlugin class CDVStatusBar > (pluginName: StatusBar) does not exist. > 2013-11-20 14:59:28.302 ProductDemo[65497:a0b] ERROR: Plugin 'StatusBar' not > found, or is not a CDVPlugin. Check your plugin mapping in config.xml. > 2013-11-20 14:59:28.303 ProductDemo[65497:a0b] -[CDVCommandQueue > executePending] [Line 117] FAILED pluginJSON = [ > "INVALID", > "StatusBar", > "overlaysWebView", > [ > true > ] > ] > I've run thought the debugging option and no errors come up so I'm not sure > what the issue is, but my config.xml is correct and everything is copied > over as far as files go. Anyone have this issue too? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5453) unnecessary items are in default application
[
https://issues.apache.org/jira/browse/CB-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828036#comment-13828036
]
Braden Shepherdson commented on CB-5453:
I vaguely recall a bug for this, to set up the default project so that it puts
these splash screens under {{merges/}}, especially since 90% of the disk usage
is for the huge Retina iPad splashes. The trouble is that this isn't supported
currently, and we just have the template blindly becoming the {{www/}}.
Honestly, I would support their removal, since they can be replaced by an
example in the docs, or even a working example in a repo somewhere, without
requiring manual steps from app devs to get rid of them.
> unnecessary items are in default application
>
>
> Key: CB-5453
> URL: https://issues.apache.org/jira/browse/CB-5453
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
>Reporter: Marcel Kinard
>Priority: Minor
>
> After building an Android apk using the CLI with the "default" application
> (no customizations added), I unzipped the apk and found the following assets
> which aren't needed. The CLI should remove this based on the target platform,
> or in the worst case there should be docs on what to clean up manually by the
> appdev. Otherwise this content may creep into production apps if the appdev's
> aren't aware/careful.
> 3096 11-18-13 14:35 assets/www/res/icon/android/icon-36-ldpi.png
> 4090 11-18-13 14:35 assets/www/res/icon/android/icon-48-mdpi.png
> 6080 11-18-13 14:35 assets/www/res/icon/android/icon-72-hdpi.png
> 7685 11-18-13 14:35 assets/www/res/icon/android/icon-96-xhdpi.png
> 11401 11-18-13 14:35 assets/www/res/icon/bada/icon-128.png
> 4111 11-18-13 14:35 assets/www/res/icon/bada-wac/icon-48-type5.png
> 5758 11-18-13 14:35 assets/www/res/icon/bada-wac/icon-50-type3.png
> 7287 11-18-13 14:35 assets/www/res/icon/bada-wac/icon-80-type4.png
> 7287 11-18-13 14:35 assets/www/res/icon/blackberry/icon-80.png
> 7287 11-18-13 14:35 assets/www/res/icon/blackberry10/icon-80.png
> 7869 11-18-13 14:35 assets/www/res/icon/ios/icon-57-2x.png
> 3908 11-18-13 14:35 assets/www/res/icon/ios/icon-57.png
> 11706 11-18-13 14:35 assets/www/res/icon/ios/icon-72-2x.png
> 4944 11-18-13 14:35 assets/www/res/icon/ios/icon-72.png
> 11401 11-18-13 14:35 assets/www/res/icon/tizen/icon-128.png
> 5463 11-18-13 14:35 assets/www/res/icon/webos/icon-64.png
> 22878 11-18-13 14:35
> assets/www/res/icon/windows-phone/icon-173-tile.png
> 4111 11-18-13 14:35 assets/www/res/icon/windows-phone/icon-48.png
> 7324 11-18-13 14:35 assets/www/res/icon/windows-phone/icon-62-tile.png
>218302 11-18-13 14:35
> assets/www/res/screen/android/screen-hdpi-landscape.png
>222148 11-18-13 14:35
> assets/www/res/screen/android/screen-hdpi-portrait.png
> 42616 11-18-13 14:35
> assets/www/res/screen/android/screen-ldpi-landscape.png
> 42034 11-18-13 14:35
> assets/www/res/screen/android/screen-ldpi-portrait.png
> 92347 11-18-13 14:35
> assets/www/res/screen/android/screen-mdpi-landscape.png
> 90555 11-18-13 14:35
> assets/www/res/screen/android/screen-mdpi-portrait.png
>489604 11-18-13 14:35
> assets/www/res/screen/android/screen-xhdpi-landscape.png
>504508 11-18-13 14:35
> assets/www/res/screen/android/screen-xhdpi-portrait.png
>222148 11-18-13 14:35 assets/www/res/screen/bada/screen-portrait.png
> 90555 11-18-13 14:35 assets/www/res/screen/bada-wac/screen-type3.png
>222148 11-18-13 14:35 assets/www/res/screen/bada-wac/screen-type4.png
>107580 11-18-13 14:35 assets/www/res/screen/bada-wac/screen-type5.png
> 16776 11-18-13 14:35 assets/www/res/screen/blackberry/screen-225.png
> 60771 11-18-13 14:35
> assets/www/res/screen/blackberry10/splash-1280x768.png
> 50431 11-18-13 14:35
> assets/www/res/screen/blackberry10/splash-720x720.png
> 57145 11-18-13 14:35
> assets/www/res/screen/blackberry10/splash-768x1280.png
> 1534088 11-18-13 14:35
> assets/www/res/screen/ios/screen-ipad-landscape-2x.png
>407370 11-18-13 14:35
> assets/www/res/screen/ios/screen-ipad-landscape.png
> 1610434 11-18-13 14:35
> assets/www/res/screen/ios/screen-ipad-portrait-2x.png
>422441 11-18-13 14:35 assets/www/res/screen/ios/screen-ipad-portrait.png
>339639 11-18-13 14:35
> assets/www/res/screen/ios/screen-iphone-landscape-2x.png
> 92301 11-18-13 14:35
> assets/www/res/screen/ios/screen-iphone-landscape.png
>350593 11-18-13 14:35
> assets/www/res/screen/ios/screen-iphone-portrait-2x.png
> 34225 11-18-13 14:35
> assets/www/r
[jira] [Commented] (CB-5338) Android API Level SHOULD NOT be hardcoded in the CLI
[ https://issues.apache.org/jira/browse/CB-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826901#comment-13826901 ] Braden Shepherdson commented on CB-5338: This is a symptom of a larger dumb thing in the CLI; which is that the Android parser's check_requirements does the checks itself, rather than calling the platform check_reqs script. > Android API Level SHOULD NOT be hardcoded in the CLI > > > Key: CB-5338 > URL: https://issues.apache.org/jira/browse/CB-5338 > Project: Apache Cordova > Issue Type: Bug > Components: Android, App Hello World, CLI >Affects Versions: 3.1.0 > Environment: Windows 7 X64 >Reporter: Rick Gommers >Assignee: Braden Shepherdson > Labels: android, api, platform, sdk > > Situation: I have re-downloaded my ADT bundle from developer.android.com > This bundle comes with the Android api lvl 18 pre-installed. > I have updated everything that needs an update, but I have not installed any > new SDK's. > Question: Upon executing the command: 'cordova add platform android' I get > the following error: > C:\cordovaprojects\test>cordova platform add android > Checking Android requirements... > [Error: Please install Android target 17 (the Android 4.2 SDK). Make sure you > have the latest Android tools installed as well. Run `android` from your > command-line to install/update any missing SDKs or tools.] > Is it really nescessary to have Android api lvl 17 installed? I want to limit > the time for our users to set everything up, so it would be helpful if we > could use the Api lvl 18 that comes preinstalled with ADT bundle. > Thx in advance! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5397) "cordova prepare ios" overwrites existing source code files/directories
[ https://issues.apache.org/jira/browse/CB-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826588#comment-13826588 ] Braden Shepherdson commented on CB-5397: The intended use of Xcode is as a build system and launcher for the emulator. The native code files are not overwritten on prepare, only the www files. The correct place to edit the www files is in $PROJECT/www, not $PROJECT/platforms/ios/www. The documentation should be loud about this, rather than nearly silent. You can use Xcode for editing the www files, but you need to explicitly point it at the $PROJECT/www files, not the www directly it has indexed. We recognize that this is confusing and lame, but it's out of our hands. Xcode doesn't handle symlinks nicely, or we would symlink the files instead of copying them. (It will load the file correctly from the symlink, but when you save it'll overwrite the link with a copy, if I remember correctly.) We are trying to avoid mixing your app with plugin assets, to avoid collisions and so on. > "cordova prepare ios" overwrites existing source code files/directories > --- > > Key: CB-5397 > URL: https://issues.apache.org/jira/browse/CB-5397 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.1.0 > Environment: MacOS 10.8.5 > XCode 5.01 >Reporter: Tom Ernhardt > > The cordova command line "cordova prepare ios" clobbers user-created source > code files/directories without warning > Steps to reproduce: > # create a test app > cordova create test com.test test > cd test > cordova platform add ios > # add a plugin > cordova plugin add https://github.com/apache/cordova-plugin-device.git > cordova prepare ios > Then open the generated Xcode project in Xcode > Add some source code files > # Now add a different plugin > cordova plugin add https://github.com/apache/cordova-plugin-console.git > # WARNING THIS WILL DELETE YOUR APP'S SOURCE CODE FILES > cordova prepare ios > All the source code files and directories that you created in > /platforms/ios/www/ > have just been deleted by the cordova CLI without any warning! -- 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=13823739#comment-13823739
]
Braden Shepherdson commented on CB-5183:
I already made that edit and merged it in.
> 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: Josh Soref
>Priority: Minor
> Attachments: cordova_wp8_wp7_cli.patch
>
>
> 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-5397) "cordova prepare ios" overwrites existing source code files/directories
[ https://issues.apache.org/jira/browse/CB-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5397: --- Working As Intended. The cordova prepare (run after platform add and plugin add/rm) step copies files into the platforms/* directories from the top level. Editing things in platforms/* by hand is not safe. There's no such thing as "user-created source files" in cordova-cli, the supported way to add custom native code to a project is by creating a plugin. I won't close this, because we should review the documentation to make sure this is clearly noted. > "cordova prepare ios" overwrites existing source code files/directories > --- > > Key: CB-5397 > URL: https://issues.apache.org/jira/browse/CB-5397 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.1.0 > Environment: MacOS 10.8.5 > XCode 5.01 >Reporter: Tom Ernhardt > > The cordova command line "cordova prepare ios" clobbers user-created source > code files/directories without warning > Steps to reproduce: > # create a test app > cordova create test com.test test > cd test > cordova platform add ios > # add a plugin > cordova plugin add https://github.com/apache/cordova-plugin-device.git > cordova prepare ios > Then open the generated Xcode project in Xcode > Add some source code files > # Now add a different plugin > cordova plugin add https://github.com/apache/cordova-plugin-console.git > # WARNING THIS WILL DELETE YOUR APP'S SOURCE CODE FILES > cordova prepare ios > All the source code files and directories that you created in > /platforms/ios/www/ > have just been deleted by the cordova CLI without any warning! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4731) Adding config entries in plugin.xml results in duplicate .plist entries
[
https://issues.apache.org/jira/browse/CB-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822616#comment-13822616
]
Braden Shepherdson commented on CB-4731:
If you're using cordova-cli, you can add a post-prepare hook to add this entry
to the newly created plist file, exactly once.
As to the bugs, there are two related problems here. One is that spaces are
getting added to places they shouldn't be; that bug is likely in the plist npm
module for handling plist files, see [here|https://npmjs.org/package/plist]. It
may instead be in the Plugman code, not certain.
The bug of adding these entries more than once is definitely in the Plugman
code. There is sophisticated logic for XML files to de-dupe each entry, keeping
a count of how many times we've been told to add it, so that we get a single
entry that isn't removed until the last plugin that wanted the entry is
uninstalled.
> Adding config entries in plugin.xml results in duplicate .plist entries
> ---
>
> Key: CB-4731
> URL: https://issues.apache.org/jira/browse/CB-4731
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 3.0.0
> Environment: macosx
>Reporter: Tim Croydon
>Assignee: Braden Shepherdson
>Priority: Minor
>
> I have the following in the plugin.xml file for a custom plugin:
> {code}
>
>
>
>location
>voip
>
>
>
> {code}
> However, this does not generate the expected entries in the .plist file. I
> get:
> {code}
> UIBackgroundModes
>
> location
> voip
> location
> voip
>
> {code}
> i.e. elements are repeated. I have tried with a single element in the source
> plugin.xml and get the same result.
> I am using the cordova CLI to manage my plugins, platforms and build.
> (p.s. I'm new to Cordova so apologies if this is filed under the incorrect
> component)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4731) Adding config entries in plugin.xml results in duplicate .plist entries
[
https://issues.apache.org/jira/browse/CB-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822618#comment-13822618
]
Braden Shepherdson commented on CB-4731:
To be clear, I mean in the last paragraph above that XML files have that
sophisticated logic, but the separate code paths for plist evidently don't.
> Adding config entries in plugin.xml results in duplicate .plist entries
> ---
>
> Key: CB-4731
> URL: https://issues.apache.org/jira/browse/CB-4731
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 3.0.0
> Environment: macosx
>Reporter: Tim Croydon
>Assignee: Braden Shepherdson
>Priority: Minor
>
> I have the following in the plugin.xml file for a custom plugin:
> {code}
>
>
>
>location
>voip
>
>
>
> {code}
> However, this does not generate the expected entries in the .plist file. I
> get:
> {code}
> UIBackgroundModes
>
> location
> voip
> location
> voip
>
> {code}
> i.e. elements are repeated. I have tried with a single element in the source
> plugin.xml and get the same result.
> I am using the cordova CLI to manage my plugins, platforms and build.
> (p.s. I'm new to Cordova so apologies if this is filed under the incorrect
> component)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5387) NPM update not working as documented
[
https://issues.apache.org/jira/browse/CB-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822584#comment-13822584
]
Braden Shepherdson commented on CB-5387:
Tempted to close this as Working As Intended. The example from the docs is just
that, an example. You'll need to check the versions of the tools that have
actually been uploaded to npm, and choose one of them to install. Generally
speaking, simply installing the latest with {{npm update -g cordova}} will do
the right thing; we choose the "latest" version on npm carefully to be the
latest full release, skipping RCs and so on.
> NPM update not working as documented
>
>
> Key: CB-5387
> URL: https://issues.apache.org/jira/browse/CB-5387
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.0.0
> Environment: Windows 7
>Reporter: John M. Wargo
>
> I’m currently at CLI 3.0.9 and tried to update to 3.1.0 (per the instructions
> in the docs here:
> http://cordova.apache.org/docs/en/3.1.0/guide_cli_index.md.html#The%20Command-line%20Interface)
> using:
> npm update -g cordova@3.1.0
> and nothing happened. Cordova stayed at 3.0.9.
> When I do:
> npm update -g cordova
> It successfully updates me to 3.1.0-0.2.0
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> C:\Users\I833153\dev\test>cordova -v
> 3.0.9
> C:\Users\I833153\dev\test>npm update -g cordova@3.1.0
> C:\Users\I833153\dev\test>cordova -v
> 3.0.9
> C:\Users\I833153\dev\test>npm update -g cordova
> npm http GET https://registry.npmjs.org/cordova
> npm http GET https://registry.npmjs.org/cordova
> npm http GET https://registry.npmjs.org/cordova
> npm http GET https://registry.npmjs.org/cordova/3.1.0-0.2.0
> npm http GET https://registry.npmjs.org/cordova/3.1.0-0.2.0
> npm http GET https://registry.npmjs.org/cordova/3.1.0-0.2.0
> npm http GET https://registry.npmjs.org/ncallbacks/1.0.0
> npm http GET https://registry.npmjs.org/colors
> npm http GET https://registry.npmjs.org/ripple-emulator/0.9.18
> npm http GET https://registry.npmjs.org/tar
> npm http GET https://registry.npmjs.org/prompt/0.2.7
> npm http GET https://registry.npmjs.org/plist
> npm http GET https://registry.npmjs.org/request/2.22.0
> npm http GET https://registry.npmjs.org/xcode/0.5.1
> npm http GET https://registry.npmjs.org/shelljs/0.1.2
> npm http GET https://registry.npmjs.org/mime
> npm http GET https://registry.npmjs.org/optimist/0.6.0
> npm http GET https://registry.npmjs.org/express/3.0.0
> npm http GET https://registry.npmjs.org/follow-redirects
> npm http GET https://registry.npmjs.org/npm
> npm http GET https://registry.npmjs.org/open/0.0.3
> npm http GET https://registry.npmjs.org/elementtree/0.1.5
> npm http GET https://registry.npmjs.org/semver/1.1.0
> npm http GET https://registry.npmjs.org/q
> npm http GET https://registry.npmjs.org/glob
> npm http GET https://registry.npmjs.org/plugman
> npm http GET https://registry.npmjs.org/ncallbacks/1.0.0
> npm http GET https://registry.npmjs.org/colors
> npm http GET https://registry.npmjs.org/ripple-emulator/0.9.18
> npm http GET https://registry.npmjs.org/tar
> npm http GET https://registry.npmjs.org/prompt/0.2.7
> npm http GET https://registry.npmjs.org/plist
> npm http GET https://registry.npmjs.org/request/2.22.0
> npm http GET https://registry.npmjs.org/xcode/0.5.1
> npm http GET https://registry.npmjs.org/shelljs/0.1.2
> npm http GET https://registry.npmjs.org/mime
> npm http GET https://registry.npmjs.org/optimist/0.6.0
> npm http GET https://registry.npmjs.org/express/3.0.0
> npm http GET https://registry.npmjs.org/follow-redirects
> npm http GET https://registry.npmjs.org/npm
> npm http GET https://registry.npmjs.org/open/0.0.3
> npm http GET https://registry.npmjs.org/elementtree/0.1.5
> npm http GET https://registry.npmjs.org/semver/1.1.0
> npm http GET https://registry.npmjs.org/q
> npm http GET https://registry.npmjs.org/glob
> npm http GET https://registry.npmjs.org/plugman
> npm http GET https://registry.npmjs.org/ncallbacks/1.0.0
> npm http GET https://registry.npmjs.org/colors
> npm http GET https://registry.npmjs.org/ripple-emulator/0.9.18
> npm http GET https://registry.npmjs.org/tar
> npm http GET https://registry.npmjs.org/prompt/0.2.7
> npm http GET https://registry.npmjs.org/plist
> npm http GET https://registry.npmjs.org/request/2.22.0
> npm http GET https://registry.npmjs.org/xcode/0.5.1
> npm http GET https://registry.npmjs.org/shelljs/0.1.2
> npm http GET https://registry.npmjs.org/mime
> npm http GET https://registry.npmjs.org/optimist/0.6.0
> npm http GET https://registry.npmjs.org/express/3.0.0
> npm http GET https://registry.npmjs.org/follow-redirects
> npm http GET https://registry.npmjs.org/npm
> npm http GET https://registry.npmjs.org/ope
[jira] [Created] (CB-5384) Runtime plugin discovery on WP8
Braden Shepherdson created CB-5384: -- Summary: Runtime plugin discovery on WP8 Key: CB-5384 URL: https://issues.apache.org/jira/browse/CB-5384 Project: Apache Cordova Issue Type: Sub-task Components: WP8 Reporter: Braden Shepherdson Assignee: Jesse MacFadyen Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5385) Runtime plugin discovery on Firefox
Braden Shepherdson created CB-5385: -- Summary: Runtime plugin discovery on Firefox Key: CB-5385 URL: https://issues.apache.org/jira/browse/CB-5385 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: Braden Shepherdson Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5381) Runtime plugin discovery on iOS
Braden Shepherdson created CB-5381: -- Summary: Runtime plugin discovery on iOS Key: CB-5381 URL: https://issues.apache.org/jira/browse/CB-5381 Project: Apache Cordova Issue Type: Sub-task Components: iOS Reporter: Braden Shepherdson Assignee: Braden Shepherdson Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5383) Runtime plugin discovery on WP7
Braden Shepherdson created CB-5383: -- Summary: Runtime plugin discovery on WP7 Key: CB-5383 URL: https://issues.apache.org/jira/browse/CB-5383 Project: Apache Cordova Issue Type: Sub-task Components: WP7 Reporter: Braden Shepherdson Assignee: Jesse MacFadyen Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5380) Runtime plugin discovery on Android
Braden Shepherdson created CB-5380: -- Summary: Runtime plugin discovery on Android Key: CB-5380 URL: https://issues.apache.org/jira/browse/CB-5380 Project: Apache Cordova Issue Type: Sub-task Components: Android Reporter: Braden Shepherdson Assignee: Braden Shepherdson Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5386) Runtime plugin discovery on Windows8
Braden Shepherdson created CB-5386: -- Summary: Runtime plugin discovery on Windows8 Key: CB-5386 URL: https://issues.apache.org/jira/browse/CB-5386 Project: Apache Cordova Issue Type: Sub-task Components: Windows 8 Reporter: Braden Shepherdson Assignee: Jesse MacFadyen Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5382) Runtime plugin discovery on BB10
Braden Shepherdson created CB-5382: -- Summary: Runtime plugin discovery on BB10 Key: CB-5382 URL: https://issues.apache.org/jira/browse/CB-5382 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry Reporter: Braden Shepherdson Fix For: 3.3.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5379) Runtime discovery of installed plugins
Braden Shepherdson created CB-5379:
--
Summary: Runtime discovery of installed plugins
Key: CB-5379
URL: https://issues.apache.org/jira/browse/CB-5379
Project: Apache Cordova
Issue Type: New Feature
Reporter: Braden Shepherdson
Assignee: Braden Shepherdson
Fix For: 3.3.0
We want Cordova apps to be able to query what plugins (and versions) are
installed at runtime.
Plugman is now injecting a tag of the kind:
{code:xml}
{code}
into the platform's config.xml. Each platform should be parsing this and
exposing it to native plugins ({{PluginManager.getPluginList()}}, or something
like that) and exposing it to Javascript via the following {{exec}} call:
{code:javascript}
cordova.exec('CordovaPlugins', 'getPluginList', [], ...);
{code}
The format of the exec call's response is a JS object whose keys are plugin IDs
and whose values are their versions.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5362) URI parameter should be able to handle local repo
[
https://issues.apache.org/jira/browse/CB-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson updated CB-5362:
---
Component/s: CLI
BlackBerry
This is a bug in the Blackberry parser in the CLI. It's blindly using the
global libDir, rather than checking for a local config and following it. See
for example the code [on
Android|https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blob;f=src/metadata/android_parser.js;h=535d5b29a7676955de1e19290609e334d83a67e5;hb=HEAD#l59].
> URI parameter should be able to handle local repo
> -
>
> Key: CB-5362
> URL: https://issues.apache.org/jira/browse/CB-5362
> Project: Apache Cordova
> Issue Type: Bug
> Components: BlackBerry, CLI
>Affects Versions: 3.1.0
>Reporter: JennyGee
>Priority: Minor
>
> (In cases where you have multiple copies of the pre-released cordova library
> and quickly switch between them.) In the project directory, you can have the
> following .cordova/config.json, and set:
> {code:javascript}
> {...
>"lib": {
>"android": {
>"version": "dev",
>"uri": "/some/local/path",
>"id": "cordova-android-dev"
>}
>}
> }
> Where the URI can specify some local REPO.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5362) URI parameter should be able to handle local repo
[
https://issues.apache.org/jira/browse/CB-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820389#comment-13820389
]
Braden Shepherdson commented on CB-5362:
I don't understand the significance of "repo" here. You mean a local checkout
of cordova-android from git? It should be working fine, just point it at the
cordova-android directory.
> URI parameter should be able to handle local repo
> -
>
> Key: CB-5362
> URL: https://issues.apache.org/jira/browse/CB-5362
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: JennyGee
>Priority: Minor
>
> (In cases where you have multiple copies of the pre-released cordova library
> and quickly switch between them.) In the project directory, you can have the
> following .cordova/config.json, and set:
> {code:javascript}
> {...
>"lib": {
>"android": {
>"version": "dev",
>"uri": "/some/local/path",
>"id": "cordova-android-dev"
>}
>}
> }
> Where the URI can specify some local REPO.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (CB-5338) Is android api lvl 17 really required to add an Android platform?
[ https://issues.apache.org/jira/browse/CB-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson reassigned CB-5338: -- Assignee: Braden Shepherdson > Is android api lvl 17 really required to add an Android platform? > - > > Key: CB-5338 > URL: https://issues.apache.org/jira/browse/CB-5338 > Project: Apache Cordova > Issue Type: Bug > Components: Android, App Hello World, CLI >Affects Versions: 3.1.0 > Environment: Windows 7 X64 >Reporter: Rick Gommers >Assignee: Braden Shepherdson > Labels: android, api, platform, sdk > > Situation: I have re-downloaded my ADT bundle from developer.android.com > This bundle comes with the Android api lvl 18 pre-installed. > I have updated everything that needs an update, but I have not installed any > new SDK's. > Question: Upon executing the command: 'cordova add platform android' I get > the following error: > C:\cordovaprojects\test>cordova platform add android > Checking Android requirements... > [Error: Please install Android target 17 (the Android 4.2 SDK). Make sure you > have the latest Android tools installed as well. Run `android` from your > command-line to install/update any missing SDKs or tools.] > Is it really nescessary to have Android api lvl 17 installed? I want to limit > the time for our users to set everything up, so it would be helpful if we > could use the Api lvl 18 that comes preinstalled with ADT bundle. > Thx in advance! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5338) Is android api lvl 17 really required to add an Android platform?
[ https://issues.apache.org/jira/browse/CB-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820215#comment-13820215 ] Braden Shepherdson commented on CB-5338: It's not "really" required, but we hard-code needing the latest API installed. The CLI was not in wide use the last time there was a new Android API version, so I'm not sure what we did last time. I have a feeling we should make this code more flexible. At any rate, we should change the harcoding to point at 18. > Is android api lvl 17 really required to add an Android platform? > - > > Key: CB-5338 > URL: https://issues.apache.org/jira/browse/CB-5338 > Project: Apache Cordova > Issue Type: Bug > Components: Android, App Hello World, CLI >Affects Versions: 3.1.0 > Environment: Windows 7 X64 >Reporter: Rick Gommers > Labels: android, api, platform, sdk > > Situation: I have re-downloaded my ADT bundle from developer.android.com > This bundle comes with the Android api lvl 18 pre-installed. > I have updated everything that needs an update, but I have not installed any > new SDK's. > Question: Upon executing the command: 'cordova add platform android' I get > the following error: > C:\cordovaprojects\test>cordova platform add android > Checking Android requirements... > [Error: Please install Android target 17 (the Android 4.2 SDK). Make sure you > have the latest Android tools installed as well. Run `android` from your > command-line to install/update any missing SDKs or tools.] > Is it really nescessary to have Android api lvl 17 installed? I want to limit > the time for our users to set everything up, so it would be helpful if we > could use the Api lvl 18 that comes preinstalled with ADT bundle. > Thx in advance! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5347) Cordova returns unknown errors messages when symlinks are pointing to bad locations
[
https://issues.apache.org/jira/browse/CB-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820198#comment-13820198
]
Braden Shepherdson commented on CB-5347:
In your project directory, you can edit .cordova/config.json, and set:
{code:javascript}
{...
"lib": {
"android": {
"version": "dev",
"uri": "/some/local/path",
"id": "cordova-android-dev"
}
}
}
{code}
and then it will copy directly from that path without using ~/.cordova/lib at
all. You can switch freely between versions by changing the uri.
> Cordova returns unknown errors messages when symlinks are pointing to bad
> locations
> ---
>
> Key: CB-5347
> URL: https://issues.apache.org/jira/browse/CB-5347
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: JennyGee
>Priority: Minor
>
> Steps to reproduce:
> 1. npm install cordova
> 2. cordova create project
> 3. cd project
> 4. cordova platform add firefoxos
> 5. cordova platform remove firefoxos
> 6. mv ~/.cordova/lib/firefoxos/cordova/3.1.0
> ~/.cordova/lib/firefoxos/cordova/3.1.0-orig
> 7. ln -s /no/such/firefoxos ~/.cordova/lib/firefoxos/cordova/3.1.0
> 8. cordova platform add firefoxos
> Actual result:
> Error that comes back that doesn't really say what is wrong:
> shell.js: internal error
> Error: EEXIST, file already exists '~/.cordova/lib/firefoxos/cordova/3.1.0'
> Expected result:
> Some sort of error that says something like this:
> [Error: Unable to fetch platform blackberry10:
> ~/.cordova/lib/firefoxos/cordova/3.1.0 points to non-existent or unreadable
> location: /no/such/firefoxos]
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5347) Cordova returns unknown errors messages when symlinks are pointing to bad locations
[ https://issues.apache.org/jira/browse/CB-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819466#comment-13819466 ] Braden Shepherdson commented on CB-5347: We recently modified the lazy loading code to not symlink into ~/.cordova/lib when you point it at a local path; instead it just copies directly from the local path. This is in the newest release of CLI, which is not tagged as "latest" on npm yet. You could install it with "npm install -g cordova@3.2.0-0.0.0". If you're putting symlinks into lib/ for other reasons, could you explain what those reasons are? Also Josh, that logic in the PR looks backwards. If it can successfully read the link, we throw an error? Shouldn't it be retrieving the link's path, then checking whether it exists? > Cordova returns unknown errors messages when symlinks are pointing to bad > locations > --- > > Key: CB-5347 > URL: https://issues.apache.org/jira/browse/CB-5347 > Project: Apache Cordova > Issue Type: Bug >Reporter: JennyGee >Priority: Minor > > Steps to reproduce: > 1. npm install cordova > 2. cordova create project > 3. cd project > 4. cordova platform add firefoxos > 5. cordova platform remove firefoxos > 6. mv ~/.cordova/lib/firefoxos/cordova/3.1.0 > ~/.cordova/lib/firefoxos/cordova/3.1.0-orig > 7. ln -s /no/such/firefoxos ~/.cordova/lib/firefoxos/cordova/3.1.0 > 8. cordova platform add firefoxos > Actual result: > Error that comes back that doesn't really say what is wrong: > shell.js: internal error > Error: EEXIST, file already exists '~/.cordova/lib/firefoxos/cordova/3.1.0' > Expected result: > Some sort of error that says something like this: > [Error: Unable to fetch platform blackberry10: > ~/.cordova/lib/firefoxos/cordova/3.1.0 points to non-existent or unreadable > location: /no/such/firefoxos] -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5230) Cordova run never completes
[ https://issues.apache.org/jira/browse/CB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819054#comment-13819054 ] Braden Shepherdson commented on CB-5230: Rick, can you try going to the platforms/android directory and running cordova\run --device directly? I'd like to see the output for a failed run, and maybe for a successful run if you can capture one. This smells like an environmental problem, if it works for others. Can one of the Cordova developers who uses Windows confirm that they can "cordova run android" successfully? > Cordova run never completes > --- > > Key: CB-5230 > URL: https://issues.apache.org/jira/browse/CB-5230 > Project: Apache Cordova > Issue Type: Bug > Components: Android, App Hello World, CLI >Affects Versions: 3.1.0 >Reporter: Rick Gommers > > Cordova run android command will never finish. Even with a newly created > hello world app. What can I do about this? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4994) Cordova prepare SyntaxError
[
https://issues.apache.org/jira/browse/CB-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817375#comment-13817375
]
Braden Shepherdson commented on CB-4994:
These will be in the next Plugman and CLI release, which we don't have firm
plans for. Our only guideline for releasing the tools is "no more frequently
than once a week", and it's been 11 days. I can do a release today, I suppose,
since we have at least one important fix in master.
The other option is to run master CLI and Plugman, the commands necessary for
which are found in the README. That'll be mirrored and rendered on
[Github|https://github.com/apache/cordova-cli] eventually, but for now see
[Apache
git|https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blob;f=README.md;h=d246cf9de898a472c57cd13969936949aceef0ba;hb=HEAD].
> Cordova prepare SyntaxError
> ---
>
> Key: CB-4994
> URL: https://issues.apache.org/jira/browse/CB-4994
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.1.0
> Environment: Xcode 5, mac 10.8.5, cordova 3.1.0-0.1.0
>Reporter: pushandplay
>Assignee: Braden Shepherdson
>Priority: Blocker
> Labels: build
> Attachments: Screen Shot 2013-10-09 at 8.31.20 PM.png
>
>
> After modify project in Xcode (change icons, capabilities and localisation
> language) can not prepare project with command "cordova prepare" and catch
> error in console
> $ cordova prepare
> { name: 'SyntaxError',
> message: 'Expected "/*", "=" or [A-Za-z0-9_] but "." found.',
> line: 382,
> column: 11 }
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-2819) Implement a cordova watch command
[
https://issues.apache.org/jira/browse/CB-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815271#comment-13815271
]
Braden Shepherdson commented on CB-2819:
cordova watch isn't very practical until prepare is faster.
> Implement a cordova watch command
> -
>
> Key: CB-2819
> URL: https://issues.apache.org/jira/browse/CB-2819
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI
>Reporter: Filip Maj
>Assignee: Braden Shepherdson
>Priority: Minor
> Labels: future
>
> a la {{grunt watch}}, will re-run {{cordova prepare}} every time the
> installed plugins change (including those installed with {{--link}}).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5299) Make cordova prepare (much) faster
Braden Shepherdson created CB-5299: -- Summary: Make cordova prepare (much) faster Key: CB-5299 URL: https://issues.apache.org/jira/browse/CB-5299 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.1.0 Reporter: Braden Shepherdson Assignee: Braden Shepherdson Prepare (especially CLI's prepare) is stupidly slow. If you have a modest www/, half a dozen plugins, and the android and ios platforms installed, it takes a couple of seconds. It should be much faster than this. This bug exists to track my efforts to measure what's slow, and improve the speed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4912) tags should support modifying attributes
[ https://issues.apache.org/jira/browse/CB-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4912. Resolution: Won't Fix Closing this as WontFix. I started implementing this today, but there are some serious problems with it. First, multiple plugins editing the same attributes result in one of them winning arbitrarily and unpredictably. Second, uninstallation is nearly impossible. If we overwrote an existing attribute value, we have no way to recover it. If we added it when it didn't exist before, we can just remove it, but only if we know that we added it. We don't have the necessary metadata, but even if we did, we would still run into cases where attribute A is originally set to false, and plugins P and Q both set it to true, and then we remove P. It restores the original value of false even though Q is installed. To solve that we need to make this logic even more complicated, so that we can find other plugins trying to set the same value and make sure their changes are still being applied. This is not the halting problem, therefore it's not impossible. However, it's a huge amount of pain and potential bugs to solve a rare use case that's pretty easy to ask a user to edit themselves, especially for AndroidManifest.xml. > tags should support modifying attributes > -- > > Key: CB-4912 > URL: https://issues.apache.org/jira/browse/CB-4912 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugman >Reporter: Braden Shepherdson >Assignee: Braden Shepherdson > > config.xml/plugin.xml tags should support adding or updating an > attribute on a tag, such as the main Android . -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5295) Platforms which are in subdirectory in repositories can't be added by cli
[ https://issues.apache.org/jira/browse/CB-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5295: --- Assignee: Braden Shepherdson (was: Maxime LUCE) I don't understand what is meant here by "platforms in a subdir". Perhaps you're being burned by the fact that the config.json file used to decide where to load libraries from is no longer $HOME/.cordova/config.json, but $PROJECT/.cordova/config.json. As far as I know there are no problems with local platform libraries, so long as you specify them correctly and in the right place. > Platforms which are in subdirectory in repositories can't be added by cli > - > > Key: CB-5295 > URL: https://issues.apache.org/jira/browse/CB-5295 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Windows 8, WP7, WP8 >Affects Versions: 3.1.0 >Reporter: Maxime LUCE >Assignee: Braden Shepherdson > > Platforms which are in a subdirectory of their repository can’t be added by > cli. > In the commit d75c0585c88ee9283db400f0c946027bd9d6e1ea in cordova-cli > repository, someone removed detection from theses platforms. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4866) Hooks executing in random order
[ https://issues.apache.org/jira/browse/CB-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4866. Resolution: Fixed Implemented this. I couldn't find the old commit, but I remade it. I also added tests that expect this sorting behavior. > Hooks executing in random order > --- > > Key: CB-4866 > URL: https://issues.apache.org/jira/browse/CB-4866 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 >Reporter: Ivan Baktsheev >Assignee: Braden Shepherdson > > hooks launch order depends on node's fs.readdirSync function. this function > ordering not guaranteed according to the > https://github.com/joyent/node/issues/2545. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4735) Support optional plugin dependancies
[ https://issues.apache.org/jira/browse/CB-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814993#comment-13814993 ] Braden Shepherdson commented on CB-4735: We now have cordova plugin rm -f, to force uninstallation. That goes a long way towards supporting the use cases requested here, although it's admittedly ugly. > Support optional plugin dependancies > > > Key: CB-4735 > URL: https://issues.apache.org/jira/browse/CB-4735 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: 3.0.0 >Reporter: Michal Mocny >Assignee: Braden Shepherdson > > plugins (and perhaps soon apps, and perhaps some future day platforms, too) > support plugin dependencies. However, right now all dependents are mandatory > for the successful use of the depending plugin. It would be nice to be able > to list optional dependencies which allow for conditional enhancement, but > are not a core requirement. > One quick example: Logger for iOS would be a nice default dependency of the > platform, but should be safely removeable, and CLI should remember and > respect the users decision to remove it if they chose to. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4729) "cordova emulate android" does not run emulator
[ https://issues.apache.org/jira/browse/CB-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4729. Resolution: Cannot Reproduce Closing this as No Repro; it's been working fine for a while. There was some confusion about whether the flag was --emulator or --emulate, but I think all the inconsistencies have been eliminated. If you're still having problems, please reopen with the output of: 1. cordova --version 2. cordova emulate android --verbose 3. cd platforms/android; cordova/run --emulator > "cordova emulate android" does not run emulator > --- > > Key: CB-4729 > URL: https://issues.apache.org/jira/browse/CB-4729 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X >Reporter: Steve Husting >Assignee: Braden Shepherdson > > When I run "cordova emulate android" then the screen flickers about 20 > seconds later, but no emulator appears. The Eclipse SDK is installed and I've > created other apps with it pre-CLI 3.0. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4923) External commands streaming output
[ https://issues.apache.org/jira/browse/CB-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4923. Resolution: Fixed csantana did this a while ago; we're using child_process.spawn, which doesn't buffer its output. > External commands streaming output > -- > > Key: CB-4923 > URL: https://issues.apache.org/jira/browse/CB-4923 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Braden Shepherdson >Assignee: Braden Shepherdson >Priority: Minor > > External commands, especially run and emulate, should stream their output in > --verbose mode, rather than buffering until the end. Just requires switching > calls from child_process.exec to something else in child_process that doesn't > buffer. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4538) Windows Phone bin/create scripts should copy check_reqs script into project/cordova folder
[ https://issues.apache.org/jira/browse/CB-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814986#comment-13814986 ] Braden Shepherdson commented on CB-4538: Another ping. Anyone with experience on Windows want to comment on this? > Windows Phone bin/create scripts should copy check_reqs script into > project/cordova folder > -- > > Key: CB-4538 > URL: https://issues.apache.org/jira/browse/CB-4538 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP7, WP8 >Affects Versions: Master >Reporter: Filip Maj >Assignee: Jesse MacFadyen > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4515) Allow CLI to specify emulator target details
[ https://issues.apache.org/jira/browse/CB-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4515. Resolution: Fixed The CLI emulate and run commands forward any unrecognized arguments (say, --ipad) to the platform scripts, so it's up to those scripts to handle and document these nonstandard arguments. > 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: Braden Shepherdson > > *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 was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4483) Route Debug Console Messages to Terminal
[
https://issues.apache.org/jira/browse/CB-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-4483.
Resolution: Fixed
This was done a long time ago, when we implemented verbosity handling. All
logging is done with emitted events now, and if the CLI is used as a module, no
logging to the console is done.
> 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: Braden Shepherdson
>
> *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 was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-4996) Run Android Emulator gives No such file or directory error
[ https://issues.apache.org/jira/browse/CB-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4996. Resolution: Fixed Fix Version/s: 3.2.0 This was a problem with unquoted paths in exec commands in the Android build scripts; they have been fixed. > Run Android Emulator gives No such file or directory error > -- > > Key: CB-4996 > URL: https://issues.apache.org/jira/browse/CB-4996 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 >Reporter: Vincentdevreede >Assignee: Braden Shepherdson >Priority: Minor > Labels: android, emulator, mac, partition, run_on_emulator, > volumes > Fix For: 3.2.0 > > > Everything is correctly set up. But when i run "phonegap run android", and it > is trying to install app on emulator its going to error. > [error] An error occurred while emulating/deploying the android > project./Volumes/Vincent de > Vreede/PhoneGap/Test/platforms/android/cordova/run: line 69: > /Volumes/Vincent: No such file or directory > /Volumes/Vincent de Vreede/PhoneGap/Test/platforms/android/cordova/run: line > 32: /Volumes/Vincent: No such file or directory > /Volumes/Vincent de Vreede/PhoneGap/Test/platforms/android/cordova/run: line > 36: /Volumes/Vincent: No such file or directory > No devices/emulators started nor images available to start. How are we > supposed to do this, then? > The problem is that he dont understand that /Volumes/Vincent de Vreede/ is my > directory and not /Volumes/Vincent/, soo he cant find the files. > I have changed my volume name to Vincentdevreede, and now its working. So the > run_on_emulator function has a bug. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4914) Cordova CLI cannot build Android project when the path contains spaces
[ https://issues.apache.org/jira/browse/CB-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4914. Resolution: Fixed Fix Version/s: 3.2.0 This was fixed some time ago in the 3.2 platform scripts for Android. I can't reproduce it with the latest Android scripts. > Cordova CLI cannot build Android project when the path contains spaces > -- > > Key: CB-4914 > URL: https://issues.apache.org/jira/browse/CB-4914 > Project: Apache Cordova > Issue Type: Bug > Components: Android, CLI >Affects Versions: 3.0.0 > Environment: Platform: Windows 7 > Cordova CLI Version: 3.0.9 >Reporter: Simon Fisher >Assignee: Lorin Beer > Fix For: 3.2.0 > > > When attempting to use the CLI to compile/build an android project, if the > path contains spaces then the command fails. > Example: > C:\my path>cordova create HelloWorld com.test.helloworld "HelloWorld" > (success) > C:\my path> cd helloworld > C:\my path\helloworld>cordova platform add android > (success) > C:\my path\helloworld>cordova prepare android > (success) > C:\my path\helloworld>cordova compile android > [Error: An error occurred while building the android project. 'C:\my' is not > recognized as an internal or external command, operable program or batch file. > ] > The same error occurs if I manually run "platforms/android/cordova/build.bat" > However if I manually run "platforms/android/ant debug" then the build > appears to succeed (at least, it gives no errors and generates an .APK file) -- 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=13814950#comment-13814950
]
Braden Shepherdson commented on CB-5218:
I like the idea of putting this metadata into that file. We need to make sure
it gets updated on a platform upgrade. We also need to be careful about
version: dev, when installing from a local directory instead of downloading.
> 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-4609) relative path to cordova.js & windows path
[
https://issues.apache.org/jira/browse/CB-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814947#comment-13814947
]
Braden Shepherdson commented on CB-4609:
I think the suggestion to use a post-prepare hook is the way to go here. The
hooks system exists to enable this sort of custom behavior, on the principle
that the last 10% of the use-cases take the other 90% of the time.
Plugman will keep doing its thing and copying into plugins/ and
cordova_plugins.js, but your post-prepare hook will run after it, and can move
them into wherever you like.
If that doesn't work, then we'll see what fixes we need to make.
> relative path to cordova.js & windows path
> --
>
> Key: CB-4609
> URL: https://issues.apache.org/jira/browse/CB-4609
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, Plugman
>Affects Versions: 3.0.0
> Environment: Window 8, node v0.10.16
>Reporter: Jonathan Bond
>Assignee: Anis Kadri
> Attachments: Result of 'plugin add'.jpg
>
>
> I'm experimenting with a new plugin:
> https://github.com/jbondc/cordova-plugin-gesture
> To reproduce:
> - Download https://github.com/jbondc/mtlhack-PhoneGap-gesture
> 1) Issue #1
> {code}
> cd cordova
> plugin add https://github.com/jbondc/cordova-plugin-gesture
> {code}
> Since cordova.js isn't in the default path (www/resources/cordova.js), the
> plugins gets copied to (www/plugins/) instead of (www/resources/js/plugins).
> The same for 'cordova_plugins.js' (see attached screenshot)
> Fix is likely in the cli/plugman to set find the appropriate root/base path
> to cordova.js
> 2) Issue #2
> Adding a plugin from a Windows path
> {code}
> cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-gesture
> {code}
> In cordova_plugins.js, I see:
> {code}
> cordova.define('cordova/plugin_list', function(require, exports, module) {
> module.exports = [
> {
> "file": "plugins\\org.apache.cordova.core.Gesture\\www\\gesture.js",
> "id": "org.apache.cordova.core.Gesture.Gesture",
> "clobbers": [
> "cordova.gesture"
> ]
> }
> ]
> });
> {code}
> That path should be normalized to:
> "plugins/org.apache.cordova.core.Gesture/www/gesture.js"
> Fix is likely in cli/plugman:
> {code}path.replace("\\", "/"){code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5288) Support fuzzy matching when using "cordova plugin add"
[ https://issues.apache.org/jira/browse/CB-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5288: --- Priority: Trivial (was: Major) This would require CLI to know a list of what plugins are available. That's possible, of course, but it may be the realm of a bash/zsh/etc. completion plugin rather than built into Cordova. I suppose we can keep this on the books with a low priority, and someone can implement it if they want to. I think it's better put into a shell plugin. > 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 >Priority: Trivial > > 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] [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-5259) CLI plugin list should show the version of the installed plugin
[
https://issues.apache.org/jira/browse/CB-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812918#comment-13812918
]
Braden Shepherdson commented on CB-5259:
There are plans to make the reporting bits of CLI much more detailed. We want
to show versions installed, dependencies, and so on. Something similar was done
for platforms a while ago, but we want to do more there as well.
These expanded reports will then be combined into a single command, probably
cordova info, that will dump a couple screenfuls of info about the tools,
platforms, plugins, and project. Then it becomes standard procedure to include
that info in any bug reports on CLI projects.
The only problem is a shortage of [round
tuits|http://en.wiktionary.org/wiki/round_tuit].
> CLI plugin list should show the version of the installed plugin
> ---
>
> Key: CB-5259
> URL: https://issues.apache.org/jira/browse/CB-5259
> Project: Apache Cordova
> Issue Type: Wish
> Components: CLI
>Affects Versions: 3.1.0
>Reporter: Peter
>Priority: Minor
>
> The *cordova plugin* list operation would be more useful if it also displayed
> the _version_ of the currently installed plugin - to help user decide if they
> needed to upgrade said plugin or not. Currently seems only way to discover
> plugin versions is to manually look in the plugin.xml file of each plugin...
> Currently cordova plugin just shows the plugin id but a simple directory
> listing of plugins would acheive pretty much the same thing in my CLI
> project. For example,
> *cordova plugin*
> {code}
> D:\IMAPS\work\trunk\SRC\IMAPSAgent3x>cordova plugin
> [ 'org.apache.cordova.battery-status',
> 'org.apache.cordova.camera',
> 'org.apache.cordova.console',
> 'org.apache.cordova.contacts',
> 'org.apache.cordova.device',
> 'org.apache.cordova.device-motion',
> 'org.apache.cordova.device-orientation',
> 'org.apache.cordova.dialogs',
> 'org.apache.cordova.file',
> 'org.apache.cordova.file-transfer',
> 'org.apache.cordova.geolocation',
> 'org.apache.cordova.globalization',
> 'org.apache.cordova.inappbrowser',
> 'org.apache.cordova.media',
> 'org.apache.cordova.media-capture',
> 'org.apache.cordova.network-information',
> 'org.apache.cordova.splashscreen',
> 'org.apache.cordova.vibration' ]
> {code}
> *dir /AD plugins*
> {code}
> D:\IMAPS\work\trunk\SRC\IMAPSAgent3x>dir /AD plugins
> Volume in drive D has no label.
> Volume Serial Number is AAB8-3216
> Directory of D:\IMAPS\work\trunk\SRC\IMAPSAgent3x\plugins
> 16/10/2013 04:57 PM .
> 16/10/2013 04:57 PM ..
> 16/10/2013 04:57 PM org.apache.cordova.battery-status
> 16/10/2013 04:57 PM org.apache.cordova.camera
> 16/10/2013 04:57 PM org.apache.cordova.console
> 16/10/2013 04:57 PM org.apache.cordova.contacts
> 16/10/2013 04:57 PM org.apache.cordova.device
> 16/10/2013 04:57 PM org.apache.cordova.device-motion
> 16/10/2013 04:57 PM org.apache.cordova.device-orientation
> 16/10/2013 04:57 PM org.apache.cordova.dialogs
> 16/10/2013 04:57 PM org.apache.cordova.file
> 16/10/2013 04:57 PM org.apache.cordova.file-transfer
> 16/10/2013 04:57 PM org.apache.cordova.geolocation
> 16/10/2013 04:57 PM org.apache.cordova.globalization
> 16/10/2013 04:57 PM org.apache.cordova.inappbrowser
> 16/10/2013 04:57 PM org.apache.cordova.media
> 16/10/2013 04:57 PM org.apache.cordova.media-capture
> 16/10/2013 04:57 PM org.apache.cordova.network-information
> 16/10/2013 04:57 PM org.apache.cordova.splashscreen
> 16/10/2013 04:57 PM org.apache.cordova.vibration
>0 File(s) 0 bytes
> 20 Dir(s) 36,917,051,392 bytes free
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-4994) Cordova prepare SyntaxError
[
https://issues.apache.org/jira/browse/CB-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-4994.
Resolution: Fixed
Assignee: Braden Shepherdson
Turns out Andrew Lunny had already fixed this in node-xcode, but hadn't pushed
a new version of. I have now pushed it as 0.6.2, and updated plugman and CLI to
depend on it.
This install is working for me now.
> Cordova prepare SyntaxError
> ---
>
> Key: CB-4994
> URL: https://issues.apache.org/jira/browse/CB-4994
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.1.0
> Environment: Xcode 5, mac 10.8.5, cordova 3.1.0-0.1.0
>Reporter: Dmitry D
>Assignee: Braden Shepherdson
>Priority: Blocker
> Labels: build
> Attachments: Screen Shot 2013-10-09 at 8.31.20 PM.png
>
>
> After modify project in Xcode (change icons, capabilities and localisation
> language) can not prepare project with command "cordova prepare" and catch
> error in console
> $ cordova prepare
> { name: 'SyntaxError',
> message: 'Expected "/*", "=" or [A-Za-z0-9_] but "." found.',
> line: 382,
> column: 11 }
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5240) cordova ripple ios doesn't work! Object function server() has no method 'config'
[
https://issues.apache.org/jira/browse/CB-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5240.
Resolution: Duplicate
Assignee: Gord
Assigning to Gord for comment, but:
Ripple is known not to work in 3.x. Gord is working on fixing it, and it's
nearly ready to rock again, but it isn't working right now.
Keep an eye out for it to be supported in a near-future release of CLI; we'll
announce it in the blog post.
> cordova ripple ios doesn't work! Object function server() has no method
> 'config'
>
>
> Key: CB-5240
> URL: https://issues.apache.org/jira/browse/CB-5240
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.1.0
> Environment: cordova cli version: 3.1.0-0.2.0
>Reporter: lmnbeyond
>Assignee: Gord
>
> When I ran "cordova ripple ios -d", the console printed the following info:
> TypeError: *Object function server(port) {*
> var projectRoot = cordova_util.isCordova(process.cwd());
> port = +port || 8000;
> if (!projectRoot) {
> throw new Error('Current working directory is not a Cordova-based
> project.');
> }
> var hooks = new hooker(projectRoot);
> return hooks.fire('before_serve')
> .then(function() {
> // Run a prepare first!
> return require('../cordova').raw.prepare([]);
> }).then(function() {
> launchServer(projectRoot, port);
> return hooks.fire('after_serve');
> });
> } *has no method 'config'*
> at CLI.module.exports
> (/usr/local/lib/node_modules/cordova/src/ripple.js:26:11)
> at new CLI (/usr/local/lib/node_modules/cordova/src/cli.js:111:30)
> at Object.
> (/usr/local/lib/node_modules/cordova/bin/cordova:41:16)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Function.Module.runMain (module.js:497:10)
> at startup (node.js:119:16)
> at node.js:901:3
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5057) Removing plugins leaves dead file links in xcode projects
[ https://issues.apache.org/jira/browse/CB-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811296#comment-13811296 ] Braden Shepherdson commented on CB-5057: You mean the case where plugin A is updated, and the new version's dependencies are different from the old? Then the answer is "Yes, sort of". It does handle that case, but only because there's no way to upgrade a plugin other than removing and re-adding it. Therefore it will delete the old dependencies (if they are no longer depended on by anything) and install all new dependencies. > Removing plugins leaves dead file links in xcode projects > - > > Key: CB-5057 > URL: https://issues.apache.org/jira/browse/CB-5057 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.0.0, 3.1.0 >Reporter: Dooms >Priority: Minor > > When removing plugins, links to the files are not removed from the xcode > project. > Example: > http://www.scribeorigins.com/files/removed_then_added_plugins.jpg -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5091) Installing a plugin using a relative path may fail
[
https://issues.apache.org/jira/browse/CB-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5091.
Resolution: Fixed
Assignee: Braden Shepherdson
> Installing a plugin using a relative path may fail
> --
>
> Key: CB-5091
> URL: https://issues.apache.org/jira/browse/CB-5091
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Reporter: Marcus Pridham
>Assignee: Braden Shepherdson
>
> If I use a relative path to install a local plugin with remote and local
> dependencies it may fail dependent on the order of the dependencies.
> My plugin has a "local" dependency and a remote dependency. The remote is
> url="https://git-wip-us.apache.org/repos/asf/cordova-plugin-dialogs.git"; />
>
> and the local is url="."/>
> You can use this repository to reproduce the issue:
> https://github.com/marcuspridham/cordova-dependency-issue
> Steps:
> 1. Install cordova cli version 3.1.0-0.1.0
> 2. Clone https://github.com/marcuspridham/cordova-dependency-issue
> 3. Create a project and add a platform with the cordova cli
> 4. From your cli project try add plugin1 using a relative patch. eg. cordova
> plugin add ../plugin-relative-issue/plugins/plugin1
> Notice the error: cd: no such file or directory:
> ../cordova-dependency-issue/plugins/plugin1
> Also the command cordova plugins returns only [ 'com.blah.plugin1',
> 'org.apache.cordova.dialogs' ] and not com.blah.plugin2.
> Problem:
> When the remote dependency is installed plugman changes the working directory
> so it can run git clone but it does not change it back.
> After the remote plugin is installed, the local plugin is installed and
> plugman will try change the directory to
> ../cordova-dependency-issue/plugins/plugin1
> but the working directory is now something like
> /private/var/folders/pl/v5hfl0zn1tn6z9j15l4j0dp8tgcp1t/T.
> Possible Fix:
> In https://github.com/apache/cordova-plugman/blob/master/src/util/plugins.js:
> Around line 43 remove this:
> {code}
> shell.cd(path.dirname(tmp_dir));
> {code}
> Around line 47 change this:
> {code}
> child_process.exec(cmd, function(err, stdout, stderr) {
> {code}
> To:
> {code}
> child_process.exec(cmd, { cwd: tmp_dir }, function(err, stdout, stderr) {
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5057) Removing plugins leaves dead file links in xcode projects
[ https://issues.apache.org/jira/browse/CB-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810514#comment-13810514 ] Braden Shepherdson commented on CB-5057: Can you please try this again with the newly-released CLI and Plugman versions? I made several fixes to the way uninstallation is handled that will probably fix this. > Removing plugins leaves dead file links in xcode projects > - > > Key: CB-5057 > URL: https://issues.apache.org/jira/browse/CB-5057 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.0.0, 3.1.0 >Reporter: Dooms >Priority: Minor > > When removing plugins, links to the files are not removed from the xcode > project. > Example: > http://www.scribeorigins.com/files/removed_then_added_plugins.jpg -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4953) Adding and removing plugins breaks build process
[ https://issues.apache.org/jira/browse/CB-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810513#comment-13810513 ] Braden Shepherdson commented on CB-4953: Can you please try this again with the newly-released CLI and Plugman? I made several fixes to the way uninstallation is handled that may be influential here. > Adding and removing plugins breaks build process > > > Key: CB-4953 > URL: https://issues.apache.org/jira/browse/CB-4953 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Mac OS X 10.8.5 > Xcode 5.0 (5A1413) + iOS 7.0 SDK > Cordova 3.0.9 >Reporter: Vladimir Riha > Attachments: output.log > > > Following steps causes that I cannot build cordova project after manipulation > with plugins > $ cordova create project > $ cd project > $ cordova platform add ios > $ cordova plugin add > https://git-wip-us.apache.org/repos/asf/cordova-plugin-contacts.git > $ cordova plugin rm org.apache.cordova.contacts > $ cordova build (finishes OK) > $ cordova plugin add > https://git-wip-us.apache.org/repos/asf/cordova-plugin-contacts.git > $ cordova build > => fails (output will be attached here) > ld: symbol(s) not found for architecture i386 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810318#comment-13810318
]
Braden Shepherdson commented on CB-5201:
I think you'll need a minSdkVersion of 11 and targetSdkVersion of 17 or
whatever you like.
> Scrolling produces artifacts on android
> ---
>
> Key: CB-5201
> URL: https://issues.apache.org/jira/browse/CB-5201
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
> android:hardwareAccelerated="true"
>Reporter: Vunda Von
> Fix For: 3.1.0
>
>
> Real simple example here with a long list of items. As you scroll, you'll
> notice that the items are blank at either end you are scrolling towards. On
> a larger list with pictures and text, you can see so much tearing and
> "tiling" as you scroll. This does not happen in chrome web browser, only
> cordova apps.
> {code}
>
>
>
> Foo
>
>
> Header
>
>
> Footer
>
> for(var i=0; i < 1000; i++){
> var foo = document.createElement('li');
> foo.innerHTML = i;
> document.getElementById('foo').appendChild(foo);
> }
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5201.
Resolution: Invalid
Not a Cordova problem, the WebView just requires handholding.
> Scrolling produces artifacts on android
> ---
>
> Key: CB-5201
> URL: https://issues.apache.org/jira/browse/CB-5201
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
> android:hardwareAccelerated="true"
>Reporter: Vunda Von
> Fix For: 3.1.0
>
>
> Real simple example here with a long list of items. As you scroll, you'll
> notice that the items are blank at either end you are scrolling towards. On
> a larger list with pictures and text, you can see so much tearing and
> "tiling" as you scroll. This does not happen in chrome web browser, only
> cordova apps.
> {code}
>
>
>
> Foo
>
>
> Header
>
>
> Footer
>
> for(var i=0; i < 1000; i++){
> var foo = document.createElement('li');
> foo.innerHTML = i;
> document.getElementById('foo').appendChild(foo);
> }
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805327#comment-13805327
]
Braden Shepherdson commented on CB-5201:
The WebView component on Android, which Cordova uses, is based on the old
Android Browser, which sucks. However, if you target at least Android 3.0, and
set hardwareAccelerated="true" *in the right place* (the
element), then it should accelerate properly, at least if you're not using
overflow: scroll (and maybe even if you do, not sure).
See
http://stackoverflow.com/questions/11653936/scrolling-performance-in-webview-for-android-jelly-bean-4-1-x
for a discussion of the problem. This is targeting an older version of
Cordova/Phonegap, but the necessary settings in the AndroidManifest.xml are the
same.
> Scrolling produces artifacts on android
> ---
>
> Key: CB-5201
> URL: https://issues.apache.org/jira/browse/CB-5201
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
> android:hardwareAccelerated="true"
>Reporter: Vunda Von
> Fix For: 3.1.0
>
>
> Real simple example here with a long list of items. As you scroll, you'll
> notice that the items are blank at either end you are scrolling towards. On
> a larger list with pictures and text, you can see so much tearing and
> "tiling" as you scroll. This does not happen in chrome web browser, only
> cordova apps.
> {code}
>
>
>
> Foo
>
>
> Header
>
>
> Footer
>
> for(var i=0; i < 1000; i++){
> var foo = document.createElement('li');
> foo.innerHTML = i;
> document.getElementById('foo').appendChild(foo);
> }
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805313#comment-13805313 ] Braden Shepherdson commented on CB-5198: Whoa, hang on. The change to add the hash has been in plugman for a long time, since Sept. 3. It was in the 0.11, 0.12, and 0.13 Plugman releases. The 3.0.0 branch of the plugins very old. Remember that the plugins have their own unique semvers now. For file-transfer above, the 3.0.0 branch dates from July 18th, and the plugin has undergone many changes since, including the removal of the .core namespace. I'm not surprised it isn't working. Since the plugins have had registry dependencies for a while now, I think the right approach is to view this as not being a regression, and move forward with the change to registry deps. The conservative users are still on 2.9. The ones who moved to 3.0 are probably already on 3.1, and will shortly follow to 3.2. No one reported the bug when we introduced it without noticing weeks ago. > Plugins with dependency's will fail with cordova 3.0 > > > Key: CB-5198 > URL: https://issues.apache.org/jira/browse/CB-5198 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer, Plugin Media Capture >Affects Versions: 3.0.0 >Reporter: Steve Gill > Fix For: 3.2.0 > > > The two plugins above have a dependency tag that downloads from the registry. > Cordova 3.0.0 doesn't have support for downloading from the registry. > If someone with cordova 3.0.0 installs the file-transfer plugin (using the > git url since that was the suggested way for 3.0), it will fail in installing > the dependency due to lack of registry support. > Suggestions > Bump the major version of these plugins and set engine tag to 3.1.0 > Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from > master. Ex. cordova plugin add > https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 > (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5192) Plugman engine check fails on Windows
[
https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5192.
Resolution: Fixed
Merged in.
> Plugman engine check fails on Windows
> -
>
> Key: CB-5192
> URL: https://issues.apache.org/jira/browse/CB-5192
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Environment: Windows
>Reporter: Sergey Grebnov
>Assignee: Braden Shepherdson
>
> Right now the simplest (and also the most correct IMO) way to specify plugin
> restrictions to specific cordova version is the following:
> plugin.xml:
>
>
>
> But in this case as per plugman current implementation and engines
> definition(plugman/src/util/default-engines.js) plugman won't be able to
> resove script because on Windows the script named 'version.bat', not just
> 'version'.
> module.exports = function(project_dir){
> return {
> 'cordova':
> { 'platform':'*', 'scriptSrc':
> path.join(project_dir,'cordova','version') }, <- works in general, but NOT
> for WP7/8
>...
> 'cordova-wp8':
> { 'platform':'wp8', 'scriptSrc':
> path.join(project_dir,'cordova','version.bat') }, <- correct location, not
> used in case of example above
> child_process.exec should correctly resolve this case (missing cmd file
> extension) but plugman check for file location so it fails to find it.
> This should affect all platforms which are supported on Windows and use .bat
> files (WP7/8, BlackBerry, Android)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Reopened] (CB-5192) Plugman engine check fails on Windows
[
https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson reopened CB-5192:
Assignee: Braden Shepherdson
It's not resolved until the code hits the Apache repos. I'll review and merge
this today.
> Plugman engine check fails on Windows
> -
>
> Key: CB-5192
> URL: https://issues.apache.org/jira/browse/CB-5192
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Environment: Windows
>Reporter: Sergey Grebnov
>Assignee: Braden Shepherdson
>
> Right now the simplest (and also the most correct IMO) way to specify plugin
> restrictions to specific cordova version is the following:
> plugin.xml:
>
>
>
> But in this case as per plugman current implementation and engines
> definition(plugman/src/util/default-engines.js) plugman won't be able to
> resove script because on Windows the script named 'version.bat', not just
> 'version'.
> module.exports = function(project_dir){
> return {
> 'cordova':
> { 'platform':'*', 'scriptSrc':
> path.join(project_dir,'cordova','version') }, <- works in general, but NOT
> for WP7/8
>...
> 'cordova-wp8':
> { 'platform':'wp8', 'scriptSrc':
> path.join(project_dir,'cordova','version.bat') }, <- correct location, not
> used in case of example above
> child_process.exec should correctly resolve this case (missing cmd file
> extension) but plugman check for file location so it fails to find it.
> This should affect all platforms which are supported on Windows and use .bat
> files (WP7/8, BlackBerry, Android)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-4976) Don't use ~/.cordova/lib during platform add when platform has been set to a local path via config.json
[ https://issues.apache.org/jira/browse/CB-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4976. Resolution: Fixed Done. This should in principle work for www too; it's just another library. But because the config.json file lives in $PROJECT/.cordova/config.json now, which doesn't exist before cordova create has already checked out the www library, we'll need some custom logic for it still. > Don't use ~/.cordova/lib during platform add when platform has been set to a > local path via config.json > --- > > Key: CB-4976 > URL: https://issues.apache.org/jira/browse/CB-4976 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Andrew Grieve >Assignee: Braden Shepherdson >Priority: Minor > > The caching of the platform within libs/ is a source of frustration to the > continuous build, and to people constantly testing the tool locally against > local platform checkouts. It causes you to sometimes not point to where you > think it's pointing if the symlink already exists and it's different from > what you specified in config.json. > I think the best thing here would be to just not use the libs/ directory at > all for the non-lazy-loaded case. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5184) CLI removes plugins when it shouldn't
[
https://issues.apache.org/jira/browse/CB-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5184.
Resolution: Fixed
> CLI removes plugins when it shouldn't
> -
>
> Key: CB-5184
> URL: https://issues.apache.org/jira/browse/CB-5184
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: Master
>Reporter: Andrew Grieve
>Assignee: Braden Shepherdson
>
> {code}
> ./cordova-mobile-spec/createmobilespec.sh
> ...
> cd mobilespec
> cordova plugin add ../cordova-labs/android-legacy-websql
> agrieve@agrieve-macbookpro ~/git/cordova/mobilespec$ cordova plugin rm
> org.apache.cordova.legacyandroidwebsql
> Uninstalling org.apache.cordova.legacyandroidwebsql from android
> Preparing android project
> Uninstalling org.apache.cordova.legacyandroidwebsql from ios
> Preparing ios project
> Deleting plugin org.apache.cordova.legacyandroidwebsql
> Found 22 removable plugins. Deleting them.
> agrieve@agrieve-macbookpro ~/git/cordova/mobilespec$ cordova plugin ls
> No plugins added. Use `cordova plugin add `.
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5187) cordova-cli on windows broken for compile, emulate, run
[ https://issues.apache.org/jira/browse/CB-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803042#comment-13803042 ] Braden Shepherdson commented on CB-5187: This is caused by the switch to child_process.spawn over .exec. .exec passes the command through the shell, subject to the usual shell expansion rules. In particular, Windows shells know to look for .bat files named after the command. But trying to execute "version" directly with .spawn will fail. We need to use os.platform to adapt for Windows, and execute foo.bat. > cordova-cli on windows broken for compile, emulate, run > --- > > Key: CB-5187 > URL: https://issues.apache.org/jira/browse/CB-5187 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: Master >Reporter: Carlos Santana > > When running cordova-cli on windows is not taking the ".bat" in the scripts > Steps to reproduce: > On Windows run > C:\Users\Carlos\Desktop> node Z:\Documents\cordova\cordova-cli\bin\cordova > create C:\Users\Carlos\Desktop\clispawn -d > Creating a new cordova project with name "HelloCordova" and id > "io.cordova.hellocordova" at location "C:\Users\Carlos\Desktop\clispawn" > Using stock cordova hello-world application. > cordova library for "www" already exists. No need to download. Continuing. > Copying stock Cordova www assets into "C:\Users\Carlos\Desktop\clispawn\www" > C:\Users\Carlos\Desktop> cd .\clispawn > C:\Users\Carlos\Desktop\clispawn> node > Z:\Documents\cordova\cordova-cli\bin\cordova platform add wp8 > Downloading cordova library for wp8... > Download complete > Checking wp8 requirements... > Creating wp8 project... > Preparing wp8 project > C:\Users\Carlos\Desktop\clispawn> node > Z:\Documents\cordova\cordova-cli\bin\cordova build -d > cordova library for "wp8" already exists. No need to download. Continuing. > Generating config.xml from defaults for platform "wp8" > Calling plugman.prepare for platform "wp8" > Preparing wp8 project > Processing configuration changes for plugins. > Iterating over installed plugins: [] > Writing out cordova_plugins.js... > Compiling app on platform "wp8" via command > "C:\Users\Carlos\Desktop\clispawn\platforms\wp8\cordova\build" > Error: spawn ENOENT > at errnoException (child_process.js:980:11) > at Process.ChildProcess._handle.onexit (child_process.js:771:34) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5145) Why are non-android resources included in platforms/android assets folder?
[
https://issues.apache.org/jira/browse/CB-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801896#comment-13801896
]
Braden Shepherdson commented on CB-5145:
Is there a reason why this isn't using merges?
> Why are non-android resources included in platforms/android assets folder?
> --
>
> Key: CB-5145
> URL: https://issues.apache.org/jira/browse/CB-5145
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.1.0
> Environment: Windows
>Reporter: Peter
>Assignee: Andrew Grieve
>Priority: Minor
> Fix For: 3.2.0
>
>
> The online guide
> http://cordova.apache.org/docs/en/edge/config_ref_images.md.html says
> {quote}
> When working in the CLI, icon source files are located within various
> platform-specific subdirectories within the project's www/res/icons
> directory. Newly created projects come with a default set of Cordova icons
> for you to replace for the platforms you wish to target.
> {quote}
> OK.
> But if I've only added the *android* platform to my CLI project then why
> would I want _non_-android resources copied into my
> platforms/_android_/assets/www/res folder?
> For example,
> {code}
> D:\IMAPS\peter>cordova create myapp com.peter myapp
> D:\IMAPS\peter>cd myapp
> D:\IMAPS\peter\myapp>cordova platform add android
> D:\IMAPS\peter\myapp>tree platforms/android/assets/www/res
> Folder PATH listing
> Volume serial number is AAB8-3216
> D:\IMAPS\PETER\MYAPP\PLATFORMS\ANDROID\ASSETS\WWW\RES
> +---icon
> ¦ +---android
> ¦ +---bada
> ¦ +---bada-wac
> ¦ +---blackberry
> ¦ +---blackberry10
> ¦ +---ios
> ¦ +---tizen
> ¦ +---webos
> ¦ +---windows-phone
> +---screen
> +---android
> +---bada
> +---bada-wac
> +---blackberry
> +---blackberry10
> +---ios
> +---tizen
> +---webos
> +---windows-phone
> D:\IMAPS\peter\myapp>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4971) Installation of plugins does not work for iOS
[ https://issues.apache.org/jira/browse/CB-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801890#comment-13801890 ] Braden Shepherdson commented on CB-4971: Could this be related to either: - The broken plugin uninstallation code that was fixed yesterday? Or, - Upgrading Xcode to 5 - perhaps the plist files changed in a way that confuses plugman? I know very little about this part of the code. Though if it's working in freshly-created 3.1 projects, that's somewhat reassuring, though still worth fixing if we can figure it out. > Installation of plugins does not work for iOS > - > > Key: CB-4971 > URL: https://issues.apache.org/jira/browse/CB-4971 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts, Plugin Device, Plugin Dialogs >Affects Versions: 3.0.0, 3.1.0 > Environment: iOS >Reporter: Oleg >Priority: Critical > Labels: ios, plugin > Fix For: Master, 3.0.0, 3.2.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Installation of iOS plugins does not work for iOS. > Update: does not work in 3.1 cordova either. > When installing the plugin via "cordova plugin add", the plugins fail to > install correctly to the iOS platform: > - source code (.js, .m, .h and .bundle) files are not copied over > - proper frameworks are not being added to the project > - config.xml file is not updated with plugin information > Tried it on Device, Contacts and Dialogs and some other plugins. > Update: tried on network-information plugin with cordova 3.1 > the workaround is to perform the above steps manually. but it is not > documented anywhere. > Note: it worked for me during one test, when the project was fresh. However > after making a few minor changes and running "cordova prepare" or "cordova > build" a few times, it stops working for iOS - i.e. you cannot add plugins > without issues above. Android works fine. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4992) CLI prematurely removes plugin dependency when two plugins share a dependency
[
https://issues.apache.org/jira/browse/CB-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-4992.
Resolution: Fixed
Fix Version/s: 3.2.0
Assignee: Braden Shepherdson
> CLI prematurely removes plugin dependency when two plugins share a dependency
> -
>
> Key: CB-4992
> URL: https://issues.apache.org/jira/browse/CB-4992
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Reporter: Andrew Grieve
>Assignee: Braden Shepherdson
> Fix For: 3.2.0
>
>
> {code}
> cordova create foo com.google.foo foo
> cd foo
> cordova platform add android
> cordova plugin add org.apache.cordova.media-capture
> cordova plugin add org.apache.cordova.file-transfer
> cordova plugin rm org.apache.cordova.media-capture
> {code}
> now:
> {code}
> $ cordova plugin ls
> [ 'org.apache.cordova.file-transfer' ]
> {code}
> and:
>
> {code}
> cordova plugin rm org.apache.cordova.file-transfer
> { [Error: ENOENT, no such file or directory
> '/Users/agrieve/git/cordova/cordova-app-harness/foo/plugins/org.apache.cordova.file/plugin.xml']
> errno: 34,
> code: 'ENOENT',
> path:
> '/Users/agrieve/git/cordova/cordova-app-harness/foo/plugins/org.apache.cordova.file/plugin.xml',
> syscall: 'open' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5056) Removing a plugin with dependencies removes the dependencies also
[ https://issues.apache.org/jira/browse/CB-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-5056. Resolution: Fixed Fix Version/s: 3.2.0 Assignee: Braden Shepherdson > Removing a plugin with dependencies removes the dependencies also > - > > Key: CB-5056 > URL: https://issues.apache.org/jira/browse/CB-5056 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Plugman >Affects Versions: 3.0.0, 3.1.0 > Environment: OSX >Reporter: Dooms >Assignee: Braden Shepherdson > Fix For: 3.2.0 > > > When upgrading a project from 3.0 to 3.1, I remove all plugins first, then > re-add all plugins. > The issue is with some plugins that have dependencies. E.g. > org.apache.cordova.file-transfer > org.apache.cordova.media > Both rely on org.apache.cordova.file. > But once one plugin removes this dependency, then other plugins that rely on > it fail: > [Error: ENOENT, no such file or directory > '.../plugins/org.apache.cordova.file/plugin.xml' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4189) Plugman uninstallPlugin plugin repo removal should work bottom-up: dependency leaves first, moving up the dependency chain
[
https://issues.apache.org/jira/browse/CB-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-4189.
Resolution: Fixed
Assignee: Braden Shepherdson (was: Mark Koudritsky)
> Plugman uninstallPlugin plugin repo removal should work bottom-up: dependency
> leaves first, moving up the dependency chain
> --
>
> Key: CB-4189
> URL: https://issues.apache.org/jira/browse/CB-4189
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugman
>Affects Versions: 2.9.0, 3.0.0
>Reporter: Filip Maj
>Assignee: Braden Shepherdson
>Priority: Minor
>
> Currently, the plugin-repo-removal code (encapsulated as the
> {{uninstallPlugin}} method) blindly removes dependent plugins recursively. It
> should probably do this in a smarter fashion, similarly to how the
> {{uninstallPlatform}} method checks for any other dependents before
> proceeding with recursive uninstalls.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5060) Plugman should not auto-remove installed plugins
[
https://issues.apache.org/jira/browse/CB-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5060.
Resolution: Fixed
Fix Version/s: 3.2.0
Assignee: Braden Shepherdson
> Plugman should not auto-remove installed plugins
>
>
> Key: CB-5060
> URL: https://issues.apache.org/jira/browse/CB-5060
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Reporter: Mike Billau
>Assignee: Braden Shepherdson
> Fix For: 3.2.0
>
>
> If you install a plugin manually as a top level plugin, but that plugin is
> also used as a dependency for a second plugin, then removing the second
> plugin *should not* remove the first plugin. Currently, this is the behavior:
> {noformat}
> cordova plugin add file
> cordova plugin add file-transfer
> cordova plugin ls
> [file, file-transfer]
> cordova plugin rm file-transfer
> cordova plugin ls
> [ ]
> {noformat}
> If you manually install a plugin, that means you are planning to use it. If
> another plugin depends on it, great, that's fine, whatever, but if you later
> decide not to use the consuming plugin, it shouldn't remove the one that you
> added.
> This is different than the reference counting issue in
> https://issues.apache.org/jira/browse/CB-5056
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4714) Allow removing a plugin that is a dependency (using -f or -force flag)
[ https://issues.apache.org/jira/browse/CB-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801017#comment-13801017 ] Braden Shepherdson commented on CB-4714: Another ping. > Allow removing a plugin that is a dependency (using -f or -force flag) > -- > > Key: CB-4714 > URL: https://issues.apache.org/jira/browse/CB-4714 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: 3.0.0 > Environment: Windows 8 >Reporter: Jonathan Bond-Caron >Assignee: Braden Shepherdson >Priority: Minor > Labels: patch > Fix For: 3.2.0 > > > Some context: > I wanted to start using the mobile spec app for cordova. The problem is I > didn't know which dependencies were required for the application. > So I created a plugin which just lists some dependencies: > https://github.com/jbondc/cordova-plugin-mobile-spec > > cordova create test > > cordova platform add android > >cordova plugin list > No plugins added. Use `cordova plugin add `. > >cordova plugin add https://github.com/jbondc/cordova-plugin-mobile-spec > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.file', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > To test a modifications/patches to a specific plugin (media-capture), I > wanted to do: > >cordova plugin rm org.apache.cordova.core.media-capture > [Error: Another top-level plugin (org.apache.cordova.core.mobile-spec) relies > on plugin org.apache.cordova.core.media-capture, therefore aborting > uninstallation > .] > A lot of dependency management systems (freebsd ports, debian packages) allow > you to forcefully remove a dependency. > That's what I'm proposing: > >cordova plugin rm org.apache.cordova.core.media-capture -f > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.mobile-spec' ] > >cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-media-capture > >cordova plugin list > [ 'org.apache.cordova.core.battery-status', > 'org.apache.cordova.core.camera', > 'org.apache.cordova.core.device', > 'org.apache.cordova.core.media-capture', > 'org.apache.cordova.core.mobile-spec' ] > It makes it easier to add/remove a plugin even if some dependencies are not > met. > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4943) Error removing plugin using cordova-cli for Windows8 3.1.x
[ https://issues.apache.org/jira/browse/CB-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-4943. Resolution: Fixed Fix Version/s: 3.1.0 > Error removing plugin using cordova-cli for Windows8 3.1.x > -- > > Key: CB-4943 > URL: https://issues.apache.org/jira/browse/CB-4943 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Plugman, Windows 8 >Affects Versions: 3.1.0 > Environment: windows8 > cordova-cli branch 3.1.x + > pull request > https://github.com/apache/cordova-cli/pull/44 > cordova-windows branch 3.1.x >Reporter: Carlos Santana >Assignee: Jesse MacFadyen > Fix For: 3.1.0 > > > cordova platform add windows8 > cordova platform rm windows8 > cordova platform add windows8 > cordova plugin add Z:\Documents\cordova-3.1.x\cordova-plugin-file -d > cordova plugin add Z:\Documents\cordova-3.1.x\cordova-plugin-camera -d > But it failed on "cordova plugin rm org.apache.cordova.camera -d" > Error: malformed document. First element should be wtf? > C:\Users\Carlos\Desktop\Win8-0928> node > Z:\Documents\cordova-3.1.x\cordova-cli\bin\cordova plugin rm > org.apache.cordova.camera -d > Calling plugman.uninstall on plugin "org.apache.cordova.camera" for platform > "windows8" > Uninstalling org.apache.cordova.camera... > Beginning processing of action stack for windows8 project... > Parsing windows8 project files... > Parsing Windows8 project files... > creating jsproj from project at : > C:\Users\Carlos\Desktop\Win8-0928\platforms\windows8\CordovaApp.jsproj > Action stack processing complete. > Writing out windows8 project files... > Preparing windows8 project... > Processing configuration changes for plugins. > Error: malformed document. First element should be > at Object.exports.parseStringSync > (Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plist\lib\plist.js:80:10) > at Object.exports.parseFileSync > (Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plist\lib\plist.js:19:19) > at > Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plugman\src\util\config-changes.js:254:67 > at Array.forEach (native) > at > Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plugman\src\util\config-changes.js:221:67 > at Array.forEach (native) > at > Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plugman\src\util\config-changes.js:219:49 > at Array.forEach (native) > at Object.module.exports.remove_plugin_changes > (Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plugman\src\util\config-changes.js:201:35) > at > Z:\Documents\cordova-3.1.x\cordova-cli\node_modules\plugman\src\util\config-changes.js:414:28 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5106) CLI test cleanup
[ https://issues.apache.org/jira/browse/CB-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-5106. Resolution: Fixed All fixed now! > CLI test cleanup > > > Key: CB-5106 > URL: https://issues.apache.org/jira/browse/CB-5106 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.1.0 > Environment: mac, windows >Reporter: Steve Gill >Assignee: Steve Gill >Priority: Critical > Fix For: 3.2.0 > > > Can't seem to get them to run on Windows since the refactor. > Have failing tests when I run npm test on my mac. > Just want to spend some time fixing up + writing new tests. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5127) Detect changes to plugins and reinstall their source on prepare
[ https://issues.apache.org/jira/browse/CB-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5127: --- Component/s: (was: CordovaJS) CLI Fix Version/s: 3.2.0 Assignee: Braden Shepherdson Issue Type: Improvement (was: Bug) Summary: Detect changes to plugins and reinstall their source on prepare (was: Plugin src (at least on Android) is not copied to the platforms directory on prepare) This is by design, sort of. Prepare is not supposed to copy plugin source code, on any platform. Therefore this isn't a bug. On the other hand, we want to add a feature where the CLI will automatically reinstall plugins that have changed locally (in plugins/) on prepare, to make plugin development easier. As part of that change, we can also make sure that plugins are reinstalled in the case where they're missing altogether. Note that if you're copying between machines but excluding platforms/, all installed plugins should be installed into any new platform that's freshly "cordova platform add"ed. What are you actually copying between machines, and what commands are you running? > Detect changes to plugins and reinstall their source on prepare > --- > > Key: CB-5127 > URL: https://issues.apache.org/jira/browse/CB-5127 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI >Affects Versions: 3.0.0 > Environment: Windows 7, cordova CLI 3.0.4 >Reporter: Kris Erickson >Assignee: Braden Shepherdson > Fix For: 3.2.0 > > > Running > cordova prepare android > copies the javascript portion of the plugin, but not the Java source on > android (haven't yet tested on IOS). Thus when the project is moved between > machines the source isn't copied if it isn't retained in the VCS or if the > user adds a platform after adding a plugin. My suggestion would be to copy > only if the source isn't there in case the user has changed the plugin. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5103) cordova emulate ios broken: --emulator vs. --emulate
[ https://issues.apache.org/jira/browse/CB-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5103: --- Component/s: CLI This might be a documentation bug. A similar problem existed in the Android platform scripts, where the usage text and code didn't agree on the spelling. Double-check what the iOS run.js script is really expecting in the code. > cordova emulate ios broken: --emulator vs. --emulate > > > Key: CB-5103 > URL: https://issues.apache.org/jira/browse/CB-5103 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, iOS >Affects Versions: Master, 3.1.0 >Reporter: Carlos Santana >Assignee: Carlos Santana > > when using "cordova emulate ios" > It doesn't launch ios simulator ios-sim never gets called > possible root cause: > cordova-cli calls "platforms/ios/cordova/run --emulator" > https://github.com/apache/cordova-cli/blob/master/src/emulate.js#L25 > But cordova/run script expects "--emulate" > https://github.com/apache/cordova-ios/blob/master/bin/templates/scripts/cordova/run#L62 > possible fix: > update run to use --emulator instead of --emulate -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5065) Using git-ref on "cordova plugin add" fails with error
[ https://issues.apache.org/jira/browse/CB-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795290#comment-13795290 ] Braden Shepherdson commented on CB-5065: I believe that extra tmp_dir is from a time when the command was 'cd "%s"; git checkout "%s"'. But that has since been replaced with passing the cwd parameter to child_process.exec. It's a bit worrying that the tests didn't catch this, though. > Using git-ref on "cordova plugin add" fails with error > -- > > Key: CB-5065 > URL: https://issues.apache.org/jira/browse/CB-5065 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > > When trying to add a plugin using a git-ref, it fails with an error: > $ ../cordova-cli/bin/cordova --verbose plugin add > https://github.com/apache/cordova-plugin-console.git#r0.2.0 > Calling plugman.fetch on plugin > "https://github.com/apache/cordova-plugin-console.git#r0.2.0"; > Fetching plugin from > "https://github.com/apache/cordova-plugin-console.git#r0.2.0";... > Fetching plugin from "https://github.com/apache/cordova-plugin-console.git";... > Fetching plugin via git-clone command: git clone > "https://github.com/apache/cordova-plugin-console.git"; > "plugman-tmp1381514955645" > Plugin "https://github.com/apache/cordova-plugin-console.git"; fetched. > Error: Error fetching plugin: Error: Command failed: error: pathspec 'r0.2.0' > did not match any file(s) known to git. > at /Users/marcelk/Developer/apache/cordova-cli/src/plugin.js:94:41 > at _rejected > (/Users/marcelk/Developer/apache/cordova-cli/node_modules/q/q.js:808:24) > at /Users/marcelk/Developer/apache/cordova-cli/node_modules/q/q.js:834:30 > at Promise.when > (/Users/marcelk/Developer/apache/cordova-cli/node_modules/plugman/node_modules/q/q.js:1079:31) > at Promise.promise.promiseDispatch > (/Users/marcelk/Developer/apache/cordova-cli/node_modules/plugman/node_modules/q/q.js:752:41) > at > /Users/marcelk/Developer/apache/cordova-cli/node_modules/plugman/node_modules/q/q.js:574:44 > at flush > (/Users/marcelk/Developer/apache/cordova-cli/node_modules/plugman/node_modules/q/q.js:108:17) > at process._tickCallback (node.js:415:13) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5058) CordovaLib xcode project gets assigned problematic Build Active Architecture Only settings.
[ https://issues.apache.org/jira/browse/CB-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5058: --- Component/s: iOS > CordovaLib xcode project gets assigned problematic Build Active Architecture > Only settings. > --- > > Key: CB-5058 > URL: https://issues.apache.org/jira/browse/CB-5058 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 3.0.0, 3.1.0 >Reporter: Dooms >Priority: Critical > > Somewhere along the way, the CordovaLib xcode project (not the application's > project which includes CordovaLib) gets Build Settings -> Build Active > Architecture Only set to "true" for Debug. This causes issues when debugging > on a device, with a warning: > ld: warning: ignoring file Build/Products/Debug-iphoneos/libCordova.a > ... > ld: symbol(s) not found for architecture armv7 > Followed by errors as CordovaLib cannot be included. > Recommend that Build Active Architecture Only should be set to "false" for > both Debug and Release, as such: > http://www.scribeorigins.com/files/CordovaLib_build_settings.jpg -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5057) Removing plugins leaves dead file links in xcode projects
[ https://issues.apache.org/jira/browse/CB-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5057: --- Component/s: Plugman > Removing plugins leaves dead file links in xcode projects > - > > Key: CB-5057 > URL: https://issues.apache.org/jira/browse/CB-5057 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.0.0, 3.1.0 >Reporter: Dooms >Priority: Minor > > When removing plugins, links to the files are not removed from the xcode > project. > Example: > http://www.scribeorigins.com/files/removed_then_added_plugins.jpg -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5056) Removing a plugin with dependencies removes the dependencies also
[ https://issues.apache.org/jira/browse/CB-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5056: --- Component/s: Plugman CLI I think this is a known issue, but it also doesn't have a bug open as far as I can see, so we'll track it here. More generally, the handling of dependencies vs. top-level plugins needs work. > Removing a plugin with dependencies removes the dependencies also > - > > Key: CB-5056 > URL: https://issues.apache.org/jira/browse/CB-5056 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Plugman >Affects Versions: 3.0.0, 3.1.0 > Environment: OSX >Reporter: Dooms > > When upgrading a project from 3.0 to 3.1, I remove all plugins first, then > re-add all plugins. > The issue is with some plugins that have dependencies. E.g. > org.apache.cordova.file-transfer > org.apache.cordova.media > Both rely on org.apache.cordova.file. > But once one plugin removes this dependency, then other plugins that rely on > it fail: > [Error: ENOENT, no such file or directory > '.../plugins/org.apache.cordova.file/plugin.xml' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5029) CLI should show plugin dependencies
[
https://issues.apache.org/jira/browse/CB-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson updated CB-5029:
---
Component/s: (was: Plugman)
CLI
Assignee: Braden Shepherdson
There are plans to improve plugin list to be *much* more detailed. Versions,
dependencies, fetched-from, and other info. I'll leave this open to track it.
> CLI should show plugin dependencies
> ---
>
> Key: CB-5029
> URL: https://issues.apache.org/jira/browse/CB-5029
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI
>Reporter: Marcel Kinard
>Assignee: Braden Shepherdson
>Priority: Minor
>
> It would be nice if the list of plugins could identify dependencies.
> For example, instead of:
> $ cordova plugin
> [ 'org.apache.cordova.file',
> 'org.apache.cordova.file-transfer' ]
> Perhaps it could say something like:
> [ 'org.apache.cordova.file',
> 'org.apache.cordova.file-transfer',
> { dependencies:
> { 'org.apache.cordova-file-transfer': [ 'org.apache.cordova.file' ] }
> } ]
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5017) There is no way to set a proxy for plugman
[ https://issues.apache.org/jira/browse/CB-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789669#comment-13789669 ] Braden Shepherdson commented on CB-5017: Oh, I wasn't expecting that answer. I think Plugman is set up to honour proxies, using the npm proxy config. So I think you should try configuring the npm proxy appropriately, and then trying it again. If it works but having all of npm proxied is inconvenient, we can looking at some way to override that with a plugman-specific proxy. > There is no way to set a proxy for plugman > -- > > Key: CB-5017 > URL: https://issues.apache.org/jira/browse/CB-5017 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.1.0 >Reporter: Mike Kwan > > Plugman tries to hit http://registry.cordova.io and in some cases we want to > hit this through a proxy. At the moment there is no way to configure this > behaviour. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5017) There is no way to set a proxy for plugman
[ https://issues.apache.org/jira/browse/CB-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789610#comment-13789610 ] Braden Shepherdson commented on CB-5017: Can you elaborate a bit? Do you mean an ordinary web proxy your company or whatever is using for net access? Or are you really asking "I need a way to have Plugman hit my registry over here some of the time, instead of the main one"? > There is no way to set a proxy for plugman > -- > > Key: CB-5017 > URL: https://issues.apache.org/jira/browse/CB-5017 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 3.1.0 >Reporter: Mike Kwan > > Plugman tries to hit http://registry.cordova.io and in some cases we want to > hit this through a proxy. At the moment there is no way to configure this > behaviour. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4971) Installation of plugins does not work for iOS
[ https://issues.apache.org/jira/browse/CB-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789263#comment-13789263 ] Braden Shepherdson commented on CB-4971: I'm not sure of the implications of the files being red in Xcode. Required by other files/specified in the plist but not present? I suppose they weren't there if you look in the directory, since you had to add the directory. Can you try to add the plugin with --verbose, and paste the output here? > Installation of plugins does not work for iOS > - > > Key: CB-4971 > URL: https://issues.apache.org/jira/browse/CB-4971 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts, Plugin Device, Plugin Dialogs >Affects Versions: 3.0.0, 3.1.0 > Environment: iOS >Reporter: Oleg >Priority: Critical > Labels: ios, plugin > Fix For: Master, 3.0.0, 3.1.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Installation of iOS plugins does not work for iOS. > Update: does not work in 3.1 cordova either. > When installing the plugin via "cordova plugin add", the plugins fail to > install correctly to the iOS platform: > - source code (.js, .m, .h and .bundle) files are not copied over > - proper frameworks are not being added to the project > - config.xml file is not updated with plugin information > Tried it on Device, Contacts and Dialogs and some other plugins. > Update: tried on network-information plugin with cordova 3.1 > the workaround is to perform the above steps manually. but it is not > documented anywhere. > Note: it worked for me during one test, when the project was fresh. However > after making a few minor changes and running "cordova prepare" or "cordova > build" a few times, it stops working for iOS - i.e. you cannot add plugins > without issues above. Android works fine. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5000) Missing update_cordova_subproject after fresh install of 3.1.0
[
https://issues.apache.org/jira/browse/CB-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5000.
Resolution: Duplicate
Fix Version/s: 3.1.0
It looks like this is a duplicate of 4883. The patch for that is checked in,
but it didn't make it into the 3.1.0 branch. It'll be in the next tools
release, probably end of this week.
> Missing update_cordova_subproject after fresh install of 3.1.0
> --
>
> Key: CB-5000
> URL: https://issues.apache.org/jira/browse/CB-5000
> Project: Apache Cordova
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Cordova 3.1.0, node 0.10.15, npm 1.3.5, OS X 10.8.5,
> XCode 5.0
>Reporter: Tony Hursh
> Fix For: 3.1.0
>
>
> A fresh install of Cordova 3.1.0 on the machine described produces several
> warning messages. After the install completes, cordova create succeeds, but
> cordova add platform fails. This issue first occurred for me after updating,
> so I tried uninstalling completely and installing from scratch. Same issue.
> Log below:
> (first removing stuff that might conflict)
> enoch:Documents tonyhursh$ sudo npm uninstall -g phonegap
> Password:
> unbuild phonegap@3.1.0-0.15.0
> enoch:Documents tonyhursh$ sudo npm uninstall -g cordova
> unbuild cordova@3.1.0-0.1.0
> enoch:Documents tonyhursh$ sudo npm install -g cordova
> (normal logs removed)
> npm WARN engine ncallbacks@1.0.0: wanted: {"node":"~0.6.7"} (current:
> {"node":"v0.10.15","npm":"1.3.5"})
> (normal logs removed)
> npm WARN package.json github-url-from-git@1.1.1 No repository field.
> /usr/local/bin/cordova -> /usr/local/lib/node_modules/cordova/bin/cordova
> (normal logs removed)
> enoch:Documents tonyhursh$ cordova create hello com.example.hello HelloWorld
> enoch:Documents tonyhursh$ cd hello
> enoch:hello tonyhursh$ cordova platform add ios
> [Error: An error occured during creation of ios sub-project.
> /Users/tonyhursh/.cordova/lib/ios/cordova/3.1.0/bin/create: line 151:
> /Users/tonyhursh/.cordova/lib/ios/cordova/3.1.0/bin/update_cordova_subproject:
> No such file or directory
> ]
> enoch:hello tonyhursh$
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5004) Can't build Android from multiple platforms
[ https://issues.apache.org/jira/browse/CB-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson updated CB-5004: --- Component/s: (was: Android) CLI Priority: Minor (was: Major) Fix Version/s: 3.2.0 Assignee: Braden Shepherdson This is not really a supported flow. That said, it should still work, and it's not clear why this is failing. The intention is that extentionless Node.js scripts and .bat wrappers get installed side by side. We execute the command without an extention: The Unixy platforms read the shebang line in the unnamed ones, Windows looks for and finds a .bat file. Possibly the Windows scripts are doing something unusual; I will investigate. > Can't build Android from multiple platforms > --- > > Key: CB-5004 > URL: https://issues.apache.org/jira/browse/CB-5004 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.0.0 > Environment: Linux (Ubuntu 13.04), Windows 7, OS X (10.8.5); cordova > 3.0.9, Android >Reporter: Erik Brommers >Assignee: Braden Shepherdson >Priority: Minor > Fix For: 3.2.0 > > > We're starting to set up Apache Cordova in a heterogeneous development > environment -- several Macs and PCs running a combination of Linux, Windows 7 > and OS X, with the code being synched via DVCS (GitHub). > With the Windows Phone and iOS platforms, it's fairly straightforward. Create > the platform on the development OS that supports it, and only use that single > development OS for the mobile app platform. With Android, however, we're > running into some weirdness with the build. Here's the scenario: > 1. On a Windows machine, drop down to the command line and run "cordova > platforms add android". Build to your heart's content and commit the changes > to Git. > 2. On a Linux or OS X machine, pull the sources down and attempt a "cordova > build android". > --> build fails due to the build script being a .bat file. > It would be great if the call to "cordova platforms add android" could emit > the proper build scripts for Windows, Linux and OS X regardless of what > platform it's being run on. That way work that's being done on one machine > could be continued on another machine without having to remove / recreate the > android platform. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4828) CLI does not properly relative symlinks that exist within www/
[ https://issues.apache.org/jira/browse/CB-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779122#comment-13779122 ] Braden Shepherdson commented on CB-4828: Meaning that the original shelljs behavior matches system cp -R? That sucks, but it should probably stay that way. It also means we need to write custom logic to recursively copy files, then. Alternatively, make this logic optional in shelljs, and make it recognize the -L option (see man cp) to read through links. > CLI does not properly relative symlinks that exist within www/ > -- > > Key: CB-4828 > URL: https://issues.apache.org/jira/browse/CB-4828 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Andrew Grieve >Assignee: Braden Shepherdson >Priority: Minor > > Reported via ML: http://markmail.org/thread/q5d4cu67psiw5fwt > It currently copies them over verbatim, and so the links become invalid. > Not sure if we should just resolve the links when copying, or copy the links > but update their paths (or create a new link that points to the old link) -- 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
