[jira] [Resolved] (CB-11517) Cordova run browser ignore dot.folder (sencha touch integration)
[ https://issues.apache.org/jira/browse/CB-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-11517. -- Resolution: Fixed > Cordova run browser ignore dot.folder (sencha touch integration) > > > Key: CB-11517 > URL: https://issues.apache.org/jira/browse/CB-11517 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: adrian >Assignee: Jesse MacFadyen >Priority: Blocker > > Hello. I encountered this issue while creating a new project in cordova with > sencha touch integration. The sencha default project has a folder named > ".sencha" which cordova ignores and doesn't copy to the virtual server. Is > there a way/workaround to exclude this folder from ignored folders? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11517) Cordova run browser ignore dot.folder (sencha touch integration)
[ https://issues.apache.org/jira/browse/CB-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457085#comment-15457085 ] ASF GitHub Bot commented on CB-11517: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/488 > Cordova run browser ignore dot.folder (sencha touch integration) > > > Key: CB-11517 > URL: https://issues.apache.org/jira/browse/CB-11517 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: adrian >Assignee: Jesse MacFadyen >Priority: Blocker > > Hello. I encountered this issue while creating a new project in cordova with > sencha touch integration. The sencha default project has a folder named > ".sencha" which cordova ignores and doesn't copy to the virtual server. Is > there a way/workaround to exclude this folder from ignored folders? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11517) Cordova run browser ignore dot.folder (sencha touch integration)
[ https://issues.apache.org/jira/browse/CB-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457082#comment-15457082 ] ASF subversion and git services commented on CB-11517: -- Commit b4b17d0b127df4cb0f8ce8a910ae4b5c0da1a51d in cordova-lib's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=b4b17d0 ] CB-11517 Allow .folder matches > Cordova run browser ignore dot.folder (sencha touch integration) > > > Key: CB-11517 > URL: https://issues.apache.org/jira/browse/CB-11517 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: adrian >Assignee: Jesse MacFadyen >Priority: Blocker > > Hello. I encountered this issue while creating a new project in cordova with > sencha touch integration. The sencha default project has a folder named > ".sencha" which cordova ignores and doesn't copy to the virtual server. Is > there a way/workaround to exclude this folder from ignored folders? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11517) Cordova run browser ignore dot.folder (sencha touch integration)
[ https://issues.apache.org/jira/browse/CB-11517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457084#comment-15457084 ] ASF subversion and git services commented on CB-11517: -- Commit 7fcc8c4aeb466aa9fc3e13541ce904611803f493 in cordova-lib's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=7fcc8c4 ] Merge branch 'CB-11517' > Cordova run browser ignore dot.folder (sencha touch integration) > > > Key: CB-11517 > URL: https://issues.apache.org/jira/browse/CB-11517 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: adrian >Assignee: Jesse MacFadyen >Priority: Blocker > > Hello. I encountered this issue while creating a new project in cordova with > sencha touch integration. The sencha default project has a folder named > ".sencha" which cordova ignores and doesn't copy to the virtual server. Is > there a way/workaround to exclude this folder from ignored folders? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11607) breakout cordova-create from cordova-lib
[ https://issues.apache.org/jira/browse/CB-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456880#comment-15456880 ] ASF GitHub Bot commented on CB-11607: - Github user stevengill commented on the issue: https://github.com/apache/cordova-lib/pull/478 Looks like this fails because cordova-create removes all listeners on events. > breakout cordova-create from cordova-lib > > > Key: CB-11607 > URL: https://issues.apache.org/jira/browse/CB-11607 > Project: Apache Cordova > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Steve Gill >Assignee: Caryn Tran > > As the title suggests, lets breakout cordova-create from cordova-lib and > publish it as its own module. It can live in the cordova-lib git repo. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11776) Can't add two plugins with different edit-config targets
[ https://issues.apache.org/jira/browse/CB-11776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456863#comment-15456863 ] ASF GitHub Bot commented on CB-11776: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/486 > Can't add two plugins with different edit-config targets > > > Key: CB-11776 > URL: https://issues.apache.org/jira/browse/CB-11776 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: CordovaCommon >Affects Versions: 1.4.0 >Reporter: Karen Tran >Assignee: Karen Tran > Labels: edit-config, triaged > Fix For: Master > > > When adding two plugins where both plugins are using edit-config, the second > plugin will have issues being added. The conflict checking for edit-config is > missing a case where the target cannot resolve to an existing target. Should > check if the target exists before proceeding. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11776) Can't add two plugins with different edit-config targets
[ https://issues.apache.org/jira/browse/CB-11776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456862#comment-15456862 ] ASF subversion and git services commented on CB-11776: -- Commit 905429cf60084d2b0781bcf5643245e78cdf3474 in cordova-lib's branch refs/heads/master from [~ktop500] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=905429c ] CB-11776 check edit-config target exists This closes #486 > Can't add two plugins with different edit-config targets > > > Key: CB-11776 > URL: https://issues.apache.org/jira/browse/CB-11776 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: CordovaCommon >Affects Versions: 1.4.0 >Reporter: Karen Tran >Assignee: Karen Tran > Labels: edit-config, triaged > Fix For: Master > > > When adding two plugins where both plugins are using edit-config, the second > plugin will have issues being added. The conflict checking for edit-config is > missing a case where the target cannot resolve to an existing target. Should > check if the target exists before proceeding. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-3232) "cordova platform add blackberry" fails on 2.7.1-rc.1
[
https://issues.apache.org/jira/browse/CB-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456783#comment-15456783
]
ASF GitHub Bot commented on CB-3232:
GitHub user infil00p opened a pull request:
https://github.com/apache/cordova-plugin-camera/pull/235
Fixes Camera issue w.r.t. content URIs by introducing android-commons
dependency
### Platforms affected
Android
### What does this PR do?
This fixes the Camera Plugin for Android Nougat
### What testing has been done on this change?
Testing against master.
### Checklist
- [x ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ x] [Reported an
issue](http://cordova.apache.org/contribute/issues.html) in the JIRA database
- [ x] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change. (There
is none yet :( )
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/infil00p/cordova-plugin-camera nougat_camera
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-camera/pull/235.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #235
commit 3d26986bfd5b7894ee16c6785f7996ef8c4b5c4f
Author: Joe Bowser
Date: 2016-07-27T21:06:07Z
CB-11625: Working on fix to API 24 no longer allowing File URIs to be
passed across intents
commit 744d72a33bfb13b6c75e48385a9cec3435cbdd41
Author: Joe Bowser
Date: 2016-07-29T16:07:03Z
Partially modified plugin.xml
commit b62fdf50f7bd18ed5c4cb9ae72fb92908529fbfb
Author: Joe Bowser
Date: 2016-07-29T20:33:51Z
Adding provider_paths.xml so this works
commit 00e0a7dc469133faf92b46f0d72112d4d873844e
Author: Joe Bowser
Date: 2016-08-03T21:43:11Z
CB-11625: Managed to get Content Providers to work with a weird mix of
Content Providers and non-Content Providers
commit f010394af8921052d565c4baf3ed40bd1170f9de
Author: Joe Bowser
Date: 2016-08-04T18:16:29Z
WTF. Directory, not file. Not sure why I did that
commit 3ed3d887ca7336534cfeb7d2146731f4e81a1203
Author: Joe Bowser
Date: 2016-08-04T18:35:39Z
BuildConfig from test project crept in source code thanks to Android
Studio, removing
commit b63a0d83e05b81deb09429776e621f0a713af43f
Author: Joe Bowser
Date: 2016-09-01T22:11:33Z
Merging API 24 code with master including large refactor
> "cordova platform add blackberry" fails on 2.7.1-rc.1
> -
>
> Key: CB-3232
> URL: https://issues.apache.org/jira/browse/CB-3232
> Project: Apache Cordova
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: BlackBerry, CLI
>Affects Versions: 2.7.0
>Reporter: Michael Brooks
>Assignee: Michael Brooks
> Fix For: 2.7.0
>
>
> The following error is thrown when running {{$ cordova platform add
> blackberry}}:
> {code}
> [Error: An error occured during creation of blackberry sub-project. Creating
> BlackBerry project...
> Updating config.xml ...
> sed:
> /Users/mwbrooks/Dropbox/Development/sandbox/myapp/platforms/blackberry/www/config.xml:
> No such file or directory
> Cleaning up ...
> Remember to update the project.properties file inside your application
> directory!
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11058) DOAP has moved
[ https://issues.apache.org/jira/browse/CB-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456579#comment-15456579 ] ASF subversion and git services commented on CB-11058: -- Commit dd6ec6824282fe6a2fd611191b3165294f1ddaec in cordova-docs's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=dd6ec68 ] CB-11058 - DOAP has moved > DOAP has moved > -- > > Key: CB-11058 > URL: https://issues.apache.org/jira/browse/CB-11058 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website > Environment: > http://svn.apache.org/repos/asf/cordova/site/infra/doap_Cordova.rdf > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml >Reporter: Sebb >Assignee: Shazron Abdullah > Labels: triaged > > The DOAP has moved. Not sure where. > Please update > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml > with the new location -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11058) DOAP has moved
[ https://issues.apache.org/jira/browse/CB-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456446#comment-15456446 ] Sebb commented on CB-11058: --- Since the site is generated from SVN one can either use the above URLs or the following ones: http://svn.apache.org/repos/asf/cordova/site/public/infra/doap_Cordova.rdf http://svn.apache.org/repos/asf/cordova/site/public/infra/doap_Cordova_PMC.rdf But that is not the issue. To repeat the problem: The file doap_Cordova.rdf has a link to doap_Cordova_PMC.rdf. This link is currently wrong; see my comment dated 21/8/2016 Please fix the URL in the file doap_Cordova.rdf so that it uses either the SVN or the website URL. It does not matter which so long as the URL is valid. > DOAP has moved > -- > > Key: CB-11058 > URL: https://issues.apache.org/jira/browse/CB-11058 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website > Environment: > http://svn.apache.org/repos/asf/cordova/site/infra/doap_Cordova.rdf > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml >Reporter: Sebb >Assignee: Shazron Abdullah > Labels: triaged > > The DOAP has moved. Not sure where. > Please update > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml > with the new location -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8978) Adding New Image Element to config.xml
[ https://issues.apache.org/jira/browse/CB-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456404#comment-15456404 ] ASF GitHub Bot commented on CB-8978: Github user dpogue commented on the issue: https://github.com/apache/cordova-android/pull/321 Thanks! I've corrected that function name > Adding New Image Element to config.xml > -- > > Key: CB-8978 > URL: https://issues.apache.org/jira/browse/CB-8978 > Project: Apache Cordova > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: CLI, CordovaLib >Affects Versions: Master > Environment: Android, iOS, WP8, Windows, Blackberry >Reporter: Karen Tran >Assignee: Karen Tran > Labels: config.xml, images > Original Estimate: 168h > Remaining Estimate: 168h > > At present, there are only an icon element and splashscreen element that > handles copying images from a source to destination in the config.xml. These > elements also only handle copying 1 image only and replacing what was > previously there as the icon.png or splash.png. > I'm creating a new tag that will copy non-main app icon images, which could > be notification icons, button icons, custom image text, etc. and not limited > to just 1 image. > Example: > > density="mdpi" /> > The required attributes will be src and name. > Depending on the directory that the image gets copied to, the width and > height attribute may not be needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11742) After upgrading to version 6.3.1, apps won't install in Android because they are detected as DOWNGRADE
[
https://issues.apache.org/jira/browse/CB-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-11742.
-
Resolution: Won't Fix
This is working exactly as intended. We removed the random version code
generation because of numerous complaints from users reaching MAX_INT due to
this ridiculous arbitrary approach.
> After upgrading to version 6.3.1, apps won't install in Android because they
> are detected as DOWNGRADE
> --
>
> Key: CB-11742
> URL: https://issues.apache.org/jira/browse/CB-11742
> Project: Apache Cordova
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Android
>Affects Versions: 6.3.1
> Environment: Developing on Windows 8.1 with node v5.1.0, cordova
> 6.3.1 for android
>Reporter: David Martinez Borque
> Labels: android, triaged
>
> I have updated to cordova 6.3.1
> Then I compile all my apps, generating new release apks (v.1.17).
> Then I try to install the new apk into an android device where I already have
> an older version of the app (v 1.16)
> When upgrading the app (adb install -r android-release.apk) I always get this
> error:
> [INSTALL_FAILED_VERSION_DOWNGRADE]
> Most curiously, when I install the new apk (with adb install -r -d) the
> Android system detects that the version of the app is 1.17!!
> > further on...<---
> I found a workaround for this problem. I modified the build.gradle file from:
> {code}
> /*
> ELSE NOTHING! DON'T MESS WITH THE VERSION CODE IF YOU DON'T HAVE TO!
> else if (!cdvVersionCode) {
> def minSdkVersion = cdvMinSdkVersion ?:
> privateHelpers.extractIntFromManifest("minSdkVersion")
> // Vary versionCode by the two most common API levels:
> // 14 is ICS, which is the lowest API level for many apps.
> // 20 is Lollipop, which is the lowest API level for the updatable
> system webview.
> if (minSdkVersion >= 20) {
> defaultConfig.versionCode += 9
> } else if (minSdkVersion >= 14) {
> defaultConfig.versionCode += 8
> }
> }
> */
> {code}
> to:
> {code}
> /*
> ELSE NOTHING! DON'T MESS WITH THE VERSION CODE IF YOU DON'T HAVE TO!
> */
> else if (!cdvVersionCode) {
> def minSdkVersion = cdvMinSdkVersion ?:
> privateHelpers.extractIntFromManifest("minSdkVersion")
> // Vary versionCode by the two most common API levels:
> // 14 is ICS, which is the lowest API level for many apps.
> // 20 is Lollipop, which is the lowest API level for the updatable
> system webview.
> if (minSdkVersion >= 20) {
> defaultConfig.versionCode =
> Integer.parseInt(defaultConfig.versionCode + '9')
> } else if (minSdkVersion >= 14) {
> defaultConfig.versionCode =
> Integer.parseInt(defaultConfig.versionCode + '8')
> }
> }
> {code}
> With this, the generated apk is not detected as a downgrade, and when I check
> the app version in Settings of the Android device, it shows the correct
> version number.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11394) backbutton eventlistener should be able to let cordova execute the default native behaviour
[ https://issues.apache.org/jira/browse/CB-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456354#comment-15456354 ] Joe Bowser commented on CB-11394: - Is this about the backbutton or menubutton? > backbutton eventlistener should be able to let cordova execute the default > native behaviour > --- > > Key: CB-11394 > URL: https://issues.apache.org/jira/browse/CB-11394 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Android >Reporter: Philipp Kursawe > > When we override the "menubutton" with a custom handler, cordova completly > skips handling of the native behaviour (as written in the docs). > It does this even though the events `defaultPrevented` property is set to > `false`. A proper implementation of event handling would look into this > property and act accordingly. > Not sure how this could be introduced now without breaking old code. > Probably old code never returns a value from the event handler. So a patch > could check if the return value is `===true` then it should perform the > default native behaviour of that button. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11770) Cordova gps location plugin return old value
[ https://issues.apache.org/jira/browse/CB-11770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-11770. - Resolution: Won't Fix That's the intended behaviour. It should find the last value that it has before it gets a fresh value. We use the browser's implementation of GPS. > Cordova gps location plugin return old value > > > Key: CB-11770 > URL: https://issues.apache.org/jira/browse/CB-11770 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Android, iOS >Reporter: Lokesh Patel > > Hi, > Cordova gpslocation plugin return old value. > When close app and next day start app device return old Gps value the first > time then after working proper. > Thanks, > Lokesh Patel -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11796) cordova-plugin-media-capture gives wrong video orientation
[ https://issues.apache.org/jira/browse/CB-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-11796: Component/s: (was: Android) > cordova-plugin-media-capture gives wrong video orientation > -- > > Key: CB-11796 > URL: https://issues.apache.org/jira/browse/CB-11796 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Plugin Media Capture >Affects Versions: 1.3.0, 6.3.1 >Reporter: Alex Rumba > Labels: android, cordova-plugin-media-capture, html5, ionic > Original Estimate: 48h > Remaining Estimate: 48h > > My cordova version is 6.3.1 and cordova-plugin-media-capture version is > 1.3.0. When i capture the video in potrait mode, the video file is played by > HTML5 player 180 degree flipped. > I am using cordova in ionic version 1.7.12 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8978) Adding New Image Element to config.xml
[ https://issues.apache.org/jira/browse/CB-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456268#comment-15456268 ] ASF GitHub Bot commented on CB-8978: Github user purplecabbage commented on the issue: https://github.com/apache/cordova-android/pull/321 bin\templates\cordova\lib\prepare.js: line 81, col 9, 'cleanFileResources' is not defined. bin\templates\cordova\lib\prepare.js: line 433, col 10, 'cleanResourceFiles' is defined but never used. > Adding New Image Element to config.xml > -- > > Key: CB-8978 > URL: https://issues.apache.org/jira/browse/CB-8978 > Project: Apache Cordova > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: CLI, CordovaLib >Affects Versions: Master > Environment: Android, iOS, WP8, Windows, Blackberry >Reporter: Karen Tran >Assignee: Karen Tran > Labels: config.xml, images > Original Estimate: 168h > Remaining Estimate: 168h > > At present, there are only an icon element and splashscreen element that > handles copying images from a source to destination in the config.xml. These > elements also only handle copying 1 image only and replacing what was > previously there as the icon.png or splash.png. > I'm creating a new tag that will copy non-main app icon images, which could > be notification icons, button icons, custom image text, etc. and not limited > to just 1 image. > Example: > > density="mdpi" /> > The required attributes will be src and name. > Depending on the directory that the image gets copied to, the width and > height attribute may not be needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10796) In-call status bar causes content to shift down (as expected) then jump up again
[ https://issues.apache.org/jira/browse/CB-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jcesarmobile resolved CB-10796. --- Resolution: Fixed Fixed in 2.1.4-dev > In-call status bar causes content to shift down (as expected) then jump up > again > > > Key: CB-10796 > URL: https://issues.apache.org/jira/browse/CB-10796 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Plugin Statusbar >Affects Versions: 3.8.0 >Reporter: Martin Baker > Labels: ios, triaged > Attachments: incall.png, nocall.png, statusbar-jump.m4v > > > Issue happens with 2.0.0, 2.1.0 and 2.1.1 but works correctly in 1.0.1 > Create a new Cordova project. Add statusbar, device and console plugins. > Run in iOS simulator and press Command-Y to toggle the enlarged "in-call > status bar". > The page content slides down as expected but then immediately jumps back up, > so it is partially covered by the status bar. > See attached screen capture. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456203#comment-15456203
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-battery-status/pull/39
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-battery-status/pull/39/commits/d8e25a1aeed12b3aa1794940230dff1e9aa52cf0)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-battery-status-pr/26//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> i
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456156#comment-15456156
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-camera/pull/234
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-camera/pull/234/commits/788b85fe90c5204cfeb2b746217f09d14ddd9fa3)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-camera-pr/77//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456056#comment-15456056
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-device-motion/pull/47
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-device-motion/pull/47/commits/ac9509160fc3e9e55361717adf8e4bb0b93ce3ab)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-motion-pr/19//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this versio
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456017#comment-15456017
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-console/pull/19
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-console/pull/19/commits/4f429484335851368df3ddebf61b8594c36db38a)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-console-pr/113//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455983#comment-15455983
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-file/pull/194
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-file/pull/194/commits/b85a483ca95c5038ee89fa237a9e986a7f6402a2)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-pr/41//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for t
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455943#comment-15455943
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-file-transfer/pull/157
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-file-transfer/pull/157/commits/62eef099971ee13d3644e9061deb8fcd30187877)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-file-transfer-pr/39//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this vers
[jira] [Reopened] (CB-11661) Camera plugin crashes on iOS 10
[ https://issues.apache.org/jira/browse/CB-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jcesarmobile reopened CB-11661: --- Assignee: (was: jcesarmobile) Reopening because only NSCameraUsageDescription was addressed on the PR, we should do the same for NSPhotoLibraryUsageDescription > Camera plugin crashes on iOS 10 > --- > > Key: CB-11661 > URL: https://issues.apache.org/jira/browse/CB-11661 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Plugin Camera >Affects Versions: 3.5.0 > Environment: iOS 10 >Reporter: jcesarmobile > > We need to add a privacy description to the plist. Since iOS 6 Apple provided > a way to show the user why a certain permission is required. In iOS 10 this > becomes mandatory, so any app not specifying the key will crash at runtime > when a permissions is requested. > This plugin requests the Camera permission, so at the very least we need to > add NSCameraUsageDescription and NSPhotoLibraryUsageDescription to the > `plist`. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455897#comment-15455897
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-contacts/pull/133
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-contacts/pull/133/commits/bbb5020a587fa54f53b151c07e8d66a60f3ef74e)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-contacts-pr/36//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding s
[jira] [Created] (CB-11801) Update DOAP PMC file with better charter
Shazron Abdullah created CB-11801: - Summary: Update DOAP PMC file with better charter Key: CB-11801 URL: https://issues.apache.org/jira/browse/CB-11801 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Website Reporter: Shazron Abdullah Horribly outdated, and we would not have favored one UI framework over the other: https://github.com/apache/cordova-docs/blob/master/www/infra/doap_Cordova_PMC.rdf -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11800) Remove/update Releases in DOAP file
Shazron Abdullah created CB-11800: - Summary: Remove/update Releases in DOAP file Key: CB-11800 URL: https://issues.apache.org/jira/browse/CB-11800 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Website Reporter: Shazron Abdullah Just put the latest release in there. https://github.com/apache/cordova-docs/blob/master/www/infra/doap_Cordova.rdf -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455874#comment-15455874
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-dialogs/pull/85
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-dialogs/pull/85/commits/badf32dbbadfd4cf6d66553fb5af62d0eb7d2c60)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-dialogs-pr/33//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sen
[jira] [Updated] (CB-11799) Update Travis CI .yml to use right Ruby and Cocoapods versions
[ https://issues.apache.org/jira/browse/CB-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-11799: -- Description: Cocopods 1.0.1 Ruby version must match (find out) Take a cue from https://github.com/CocoaPods/pod-template/blob/master/.travis.yml and others was: Cocopods 1.0.1 Ruby version must match (find out) > Update Travis CI .yml to use right Ruby and Cocoapods versions > -- > > Key: CB-11799 > URL: https://issues.apache.org/jira/browse/CB-11799 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah > Labels: easyfix > > Cocopods 1.0.1 > Ruby version must match (find out) > Take a cue from > https://github.com/CocoaPods/pod-template/blob/master/.travis.yml and others -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455840#comment-15455840
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-media/pull/115
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-media/pull/115/commits/9ff23a24c14e4b558bb72660690c3efae42ca092)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-pr/78//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any versio
[jira] [Commented] (CB-11058) DOAP has moved
[ https://issues.apache.org/jira/browse/CB-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455834#comment-15455834 ] Shazron Abdullah commented on CB-11058: --- Looks like it is under /infra https://github.com/apache/cordova-docs/search?utf8=%E2%9C%93&q=DOAP 1. http://cordova.apache.org/infra/doap_Cordova.rdf 2. http://cordova.apache.org/infra/doap_Cordova_PMC.rdf > DOAP has moved > -- > > Key: CB-11058 > URL: https://issues.apache.org/jira/browse/CB-11058 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website > Environment: > http://svn.apache.org/repos/asf/cordova/site/infra/doap_Cordova.rdf > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml >Reporter: Sebb >Assignee: Shazron Abdullah > Labels: triaged > > The DOAP has moved. Not sure where. > Please update > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml > with the new location -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11799) Update Travis CI .yml to use right Ruby and Cocoapods versions
Shazron Abdullah created CB-11799: - Summary: Update Travis CI .yml to use right Ruby and Cocoapods versions Key: CB-11799 URL: https://issues.apache.org/jira/browse/CB-11799 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: iOS Reporter: Shazron Abdullah Cocopods 1.0.1 Ruby version must match (find out) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-11791. --- Resolution: Fixed > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455800#comment-15455800 ] ASF GitHub Bot commented on CB-11791: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-ios/pull/251 > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455796#comment-15455796 ] ASF GitHub Bot commented on CB-11791: - Github user codecov-io commented on the issue: https://github.com/apache/cordova-ios/pull/251 ## [Current coverage](https://codecov.io/gh/apache/cordova-ios/pull/251?src=pr) is 55.94% (diff: 85.71%) > Merging [#251](https://codecov.io/gh/apache/cordova-ios/pull/251?src=pr) into [master](https://codecov.io/gh/apache/cordova-ios/branch/master?src=pr) will increase coverage by **0.37%** ```diff @@ master #251 diff @@ == Files11 11 Lines 1004 1017+13 Methods 144147 +3 Messages 0 0 Branches168171 +3 == + Hits558569+11 - Misses 446448 +2 Partials 0 0 ``` > Powered by [Codecov](https://codecov.io?src=pr). Last update [51d7078...439d34f](https://codecov.io/gh/apache/cordova-ios/compare/51d707838610857283ec73e6333651012bad50ed...439d34f696cde6c2812dcd2bf9837adc6564e8c9?src=pr) > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455797#comment-15455797 ] ASF subversion and git services commented on CB-11791: -- Commit aa28508d1e31e3b8c210494b73a906372d31daa3 in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=aa28508 ] CB-11791 - 'pod install' should pass in the '--verbose' flag, if set This closes #251 > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455792#comment-15455792
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-globalization/pull/50
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-globalization/pull/50/commits/9c1277d4f612af6c060ae498b7bf2da7be38fc52)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-globalization-pr/19//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this versi
[jira] [Assigned] (CB-11058) DOAP has moved
[ https://issues.apache.org/jira/browse/CB-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-11058: - Assignee: Shazron Abdullah > DOAP has moved > -- > > Key: CB-11058 > URL: https://issues.apache.org/jira/browse/CB-11058 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website > Environment: > http://svn.apache.org/repos/asf/cordova/site/infra/doap_Cordova.rdf > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml >Reporter: Sebb >Assignee: Shazron Abdullah > Labels: triaged > > The DOAP has moved. Not sure where. > Please update > https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml > with the new location -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455749#comment-15455749
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-device/pull/55
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-device/pull/55/commits/24795aec50545d47dc28919ef07df31338c1d891)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-pr/16//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
>
[jira] [Assigned] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-11791: - Assignee: Shazron Abdullah > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455746#comment-15455746 ] ASF GitHub Bot commented on CB-11791: - GitHub user shazron opened a pull request: https://github.com/apache/cordova-ios/pull/251 CB-11791 - 'pod install' should pass in the '--verbose' flag, if set You can merge this pull request into a Git repository by running: $ git pull https://github.com/shazron/cordova-ios CB-11791 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/251.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #251 commit 439d34f696cde6c2812dcd2bf9837adc6564e8c9 Author: Shazron Abdullah Date: 2016-09-01T15:07:56Z CB-11791 - 'pod install' should pass in the '--verbose' flag, if set > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11791) 'pod install' should pass in the '--verbose' flag, if set
[ https://issues.apache.org/jira/browse/CB-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-11791: -- Summary: 'pod install' should pass in the '--verbose' flag, if set (was: `pod install` should pass in the `--verbose` flag, if set) > 'pod install' should pass in the '--verbose' flag, if set > - > > Key: CB-11791 > URL: https://issues.apache.org/jira/browse/CB-11791 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah > > Passthrough the flag, if set. This is so users can see what Cocoapods is > doing behind the scenes, especially if this is the first time Cocoapods is > run, which does a full clone of the Cocoapods repo (at this time - 475MB in > size). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455702#comment-15455702
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-device-orientation/pull/29
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-device-orientation/pull/29/commits/7d72134339066c642dc39373a4a9e925c665fc60)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-device-orientation-pr/14//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455682#comment-15455682
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-media-capture/pull/68
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-media-capture/pull/68/commits/028aa7d42be19aea2c5b310f5645c3f03d3b582f)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-media-capture-pr/23//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this versio
[jira] [Updated] (CB-9596) PlatformApi master issue
[ https://issues.apache.org/jira/browse/CB-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-9596: - Description: This is the master issue for PlatformApi related work. The description is copied from https://github.com/cordova/cordova-discuss/pull/9 This proposal describes a high-level classes which describe Cordova project and Cordova platform as a strictly typed APIs: * ProjectApi - a high-level abstraction on top of cordova project, exposes project's properties and methods for project management. * PlatformApi class - further development of PlatformProject (see #4) - abstraction for single particular platform. To make the transition to new API smoother, the cordova-lib needs to be updated to expose the same class, which will work as a polyfill in case if platform doesn't provides its own PlatformApi. There also a potential problem of code duplication, since the PlatformApi needs for several classes, which currently being stored and exposed by cordova-lib: ConfigParser, PluginInfo, etc. The one of solutions of this problem - is to factor out the common classes and routines to shared module (proposed name - cordova-common), which then will be released separately. This approach is discussed in cordova-lib/#235 was: This is the master issue for PlatformApi related work. The description is copied from https://github.com/cordova/cordova-discuss/pull/9 This proposal describes a high-level classes which describes Cordova project and Cordova platform as a strictly typed APIs: * ProjectApi - a high-level abstraction on top of cordova project, exposes project's properties and methods for project management. * PlatformApi class - further development of PlatformProject (see #4) - abstraction for single particular platform. To make the transition to new API smoother, the cordova-lib needs to be updated to expose the same class, which will work as a polyfill in case if platform doesn't provides its own PlatformApi. There also a potential problem of code duplication, since the PlatformApi needs for several classes, which currently being stored and exposed by cordova-lib: ConfigParser, PluginInfo, etc. The one of solutions of this problem - is to factor out the common classes and routines to shared module (proposed name - cordova-common), which then will be released separately. This approach is discussed in cordova-lib/#235 > PlatformApi master issue > > > Key: CB-9596 > URL: https://issues.apache.org/jira/browse/CB-9596 > Project: Apache Cordova > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: CordovaCommon, CordovaLib, Plugman >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > Labels: PlatformApi, cordova-lib > > This is the master issue for PlatformApi related work. > The description is copied from > https://github.com/cordova/cordova-discuss/pull/9 > This proposal describes a high-level classes which describe Cordova project > and Cordova platform as a strictly typed APIs: > * ProjectApi - a high-level abstraction on top of cordova project, exposes > project's properties and methods for project management. > * PlatformApi class - further development of PlatformProject (see #4) - > abstraction for single particular platform. > To make the transition to new API smoother, the cordova-lib needs to be > updated to expose the same class, which will work as a polyfill in case if > platform doesn't provides its own PlatformApi. > There also a potential problem of code duplication, since the PlatformApi > needs for several classes, which currently being stored and exposed by > cordova-lib: ConfigParser, PluginInfo, etc. The one of solutions of this > problem - is to factor out the common classes and routines to shared module > (proposed name - cordova-common), which then will be released separately. > This approach is discussed in cordova-lib/#235 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11798) header cookies are persisted in app and never removed even it expires
[ https://issues.apache.org/jira/browse/CB-11798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated CB-11798: Description: When a REST service is called from my cordova app using AJAX, server is sending back session cookies (Set-Cookie headers) as part of header with expiry time.Those cookies are persisted in app & being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? was: When a REST service is called from my cordova app using AJAX, server is sending back session cookies (Set-Cookie headers) as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? > header cookies are persisted in app and never removed even it expires > - > > Key: CB-11798 > URL: https://issues.apache.org/jira/browse/CB-11798 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS, Windows >Affects Versions: 5.0.1, 6.1.1 > Environment: App is developed using HTML5 and Javascript for Windows > 8.1 and iOS. >Reporter: Ananth > Labels: ajax, cookies > > When a REST service is called from my cordova app using AJAX, server is > sending back session cookies (Set-Cookie headers) as part of header with > expiry time.Those cookies are persisted in app & being sent in the subsquitet > AJAX calls, and its never stops sending it even it the cookie is expired. > Is there any way to remove those cookies from app and stop sending it on > subsquitet AJAX calls? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455607#comment-15455607
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-geolocation/pull/80
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-geolocation/pull/80/commits/096c186770e4b8176b3ee35ab17b4709d92eb304)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-geolocation-pr/19//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
[jira] [Updated] (CB-11798) header cookies are persisted in app and never removed even it expires
[ https://issues.apache.org/jira/browse/CB-11798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated CB-11798: Environment: Cordova 6.1.1 + Windows 8.1 and iOS. (was: App is developed using HTML5 and Javascript for Windows 8.1 and iOS.) > header cookies are persisted in app and never removed even it expires > - > > Key: CB-11798 > URL: https://issues.apache.org/jira/browse/CB-11798 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS, Windows >Affects Versions: 5.0.1, 6.1.1 > Environment: Cordova 6.1.1 + Windows 8.1 and iOS. >Reporter: Ananth > Labels: ajax, cookies > > When a REST service is called from my cordova app using AJAX, server is > sending back session cookies (Set-Cookie headers) as part of header with > expiry time.Those cookies are persisted in app & being sent in the subsquitet > AJAX calls, and its never stops sending it even it the cookie is expired. > Is there any way to remove those cookies from app and stop sending it on > subsquitet AJAX calls? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11798) header cookies are persisted in app and never removed even it expires
[ https://issues.apache.org/jira/browse/CB-11798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated CB-11798: Description: When a REST service is called from my cordova app using AJAX, server is sending back session cookies (Set-Cookie headers) as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? was: When a REST service is called from my cordova app using AJAX, server is sending back session cookies as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? > header cookies are persisted in app and never removed even it expires > - > > Key: CB-11798 > URL: https://issues.apache.org/jira/browse/CB-11798 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS, Windows >Affects Versions: 5.0.1, 6.1.1 > Environment: App is developed using HTML5 and Javascript for Windows > 8.1 and iOS. >Reporter: Ananth > Labels: ajax, cookies > > When a REST service is called from my cordova app using AJAX, server is > sending back session cookies (Set-Cookie headers) as part of header with some > expiry time.Those cookies are persisted in app. That cookie is being sent in > the subsquitet AJAX calls, and its never stops sending it even it the cookie > is expired. > Is there any way to remove those cookies from app and stop sending it on > subsquitet AJAX calls? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11798) header cookies are persisted in app and never removed even it expires
[ https://issues.apache.org/jira/browse/CB-11798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ananth updated CB-11798: Description: When a REST service is called from my cordova app using AJAX, server is sending back session cookies as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? was: When a REST service is called from cordova app using AJAX, server is sending back session cookies as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? > header cookies are persisted in app and never removed even it expires > - > > Key: CB-11798 > URL: https://issues.apache.org/jira/browse/CB-11798 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS, Windows >Affects Versions: 5.0.1, 6.1.1 > Environment: App is developed using HTML5 and Javascript for Windows > 8.1 and iOS. >Reporter: Ananth > Labels: ajax, cookies > > When a REST service is called from my cordova app using AJAX, server is > sending back session cookies as part of header with some expiry time.Those > cookies are persisted in app. That cookie is being sent in the subsquitet > AJAX calls, and its never stops sending it even it the cookie is expired. > Is there any way to remove those cookies from app and stop sending it on > subsquitet AJAX calls? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455563#comment-15455563
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/184
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-inappbrowser/pull/184/commits/733f087f5037003c09414234b3cb1126dd14f940)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-inappbrowser-pr/66//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455514#comment-15455514
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-splashscreen/pull/113
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-splashscreen/pull/113/commits/67289f94353c7c8dbb2549a1f3566119d6548997)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-splashscreen-pr/25//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455497#comment-15455497
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-statusbar/pull/63
Cordova CI Build has one or more failures.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-statusbar/pull/63/commits/674d9429a33848a6802ce1ba41502ba217a78794)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-statusbar-pr/24//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for s
[jira] [Created] (CB-11798) header cookies are persisted in app and never removed even it expires
Ananth created CB-11798: --- Summary: header cookies are persisted in app and never removed even it expires Key: CB-11798 URL: https://issues.apache.org/jira/browse/CB-11798 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: iOS, Windows Affects Versions: 5.0.1, 6.1.1 Environment: App is developed using HTML5 and Javascript for Windows 8.1 and iOS. Reporter: Ananth When a REST service is called from cordova app using AJAX, server is sending back session cookies as part of header with some expiry time.Those cookies are persisted in app. That cookie is being sent in the subsquitet AJAX calls, and its never stops sending it even it the cookie is expired. Is there any way to remove those cookies from app and stop sending it on subsquitet AJAX calls? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455427#comment-15455427
]
ASF GitHub Bot commented on CB-11795:
-
Github user cordova-qa commented on the issue:
https://github.com/apache/cordova-plugin-vibration/pull/49
Cordova CI Build has completed successfully.
**Commit** -
[Link](https://github.com/apache/cordova-plugin-vibration/pull/49/commits/fda15b6584263d349686dc3e925db9281697e379)
**Dashboard** -
[Link](http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18/)
| Builder Name | Console Output | Test Report | Device Logs |
| :---: | :---: | :---: | :---:|
| [Windows 8.1 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-store/artifact/)
|
| [Windows 10 Store](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-10-store/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-10-store/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-10-store/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-10-store/artifact/)
|
| [Windows 8.1 Phone](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-phone/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-phone/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-phone/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=windows-8.1-phone/artifact/)
|
| [iOS](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=ios/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=ios/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=ios/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=ios/artifact/)
|
| [Android](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=android/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=android/console)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=android/testReport/)
| [Link](
http://cordova-ci.cloudapp.net:8080/job/cordova-plugin-vibration-pr/18//PLATFORM=android/artifact/)
|
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455341#comment-15455341
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-media-capture/pull/68
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-media-capture
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-media-capture/pull/68.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #68
commit 028aa7d42be19aea2c5b310f5645c3f03d3b582f
Author: Vladimir Kotikov
Date: 2016-08-31T13:20:05Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455351#comment-15455351
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-dialogs/pull/85
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-dialogs
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-dialogs/pull/85.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #85
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without adding corresponding
> entry to {{cordovaDependencies}} (i.e. we don't have any restrictions for
> this version in {{cordovaDependencies}}) - cordova will fetch that version
> without any checks.
> This is sounds non-obviously for me and probably there is some reason behind
> installing plugin version, which we can't verify requirements for, but this
> is how it works.
> 3. When we introduce a change that requires us to change plugin version to
> {{NEXT_MAJOR_PLUGIN_VERSION}}, we go and f
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455366#comment-15455366
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-battery-status/pull/39
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
This entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/vladimir-kotikov/cordova-plugin-battery-status CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-battery-status/pull/39.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #39
commit d8e25a1aeed12b3aa1794940230dff1e9aa52cf0
Author: Vladimir Kotikov
Date: 2016-08-31T13:09:11Z
CB-11795 Add 'protective' entry to cordovaDependencies
This entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}}
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455362#comment-15455362
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-camera/pull/234
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-camera
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-camera/pull/234.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #234
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without adding corresponding
> entry to {{cordovaDependencies}} (i.e. we don't have any restrictions for
> this version in {{cordovaDependencies}}) - cordova will fetch that version
> without any checks.
> This is sounds non-obviously for me and probably there is some reason behind
> installing plugin version, which we can't verify requirements for, but this
> is how it works.
> 3. When we introduce a change that requires us to change plugin version to
> {{NEXT_MAJOR_PLUGIN_VERSION}}, we go and f
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455356#comment-15455356
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-device-motion/pull/47
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-device-motion
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-device-motion/pull/47.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #47
commit ac9509160fc3e9e55361717adf8e4bb0b93ce3ab
Author: Vladimir Kotikov
Date: 2016-08-31T13:34:34Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455358#comment-15455358
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-contacts/pull/133
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-contacts
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-contacts/pull/133.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #133
commit bbb5020a587fa54f53b151c07e8d66a60f3ef74e
Author: Vladimir Kotikov
Date: 2016-08-31T13:30:53Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released wi
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455360#comment-15455360
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-console/pull/19
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-console
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-console/pull/19.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #19
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without adding corresponding
> entry to {{cordovaDependencies}} (i.e. we don't have any restrictions for
> this version in {{cordovaDependencies}}) - cordova will fetch that version
> without any checks.
> This is sounds non-obviously for me and probably there is some reason behind
> installing plugin version, which we can't verify requirements for, but this
> is how it works.
> 3. When we introduce a change that requires us to change plugin version to
> {{NEXT_MAJOR_PLUGIN_VERSION}}, we go and f
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455329#comment-15455329
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-statusbar/pull/63
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-statusbar
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-statusbar/pull/63.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #63
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without adding corresponding
> entry to {{cordovaDependencies}} (i.e. we don't have any restrictions for
> this version in {{cordovaDependencies}}) - cordova will fetch that version
> without any checks.
> This is sounds non-obviously for me and probably there is some reason behind
> installing plugin version, which we can't verify requirements for, but this
> is how it works.
> 3. When we introduce a change that requires us to change plugin version to
> {{NEXT_MAJOR_PLUGIN_VERSION}}, we go
[jira] [Commented] (CB-3232) "cordova platform add blackberry" fails on 2.7.1-rc.1
[
https://issues.apache.org/jira/browse/CB-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455331#comment-15455331
]
ASF GitHub Bot commented on CB-3232:
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-network-information/pull/47
The entry is required to protect end-users from fetching edge version…
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
…s of the plugin by incompatible version of cordova. This also assumes that
we will not introduce any regressions in compatibility w/ cordova in minor and
patch releases. On every major release we will need to add similar entry with
_next_ major version.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/vladimir-kotikov/cordova-plugin-network-information CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-network-information/pull/47.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #47
commit a774585f2944ac5d4d0b0d3892f02d2fefc3172f
Author: Vladimir Kotikov
Date: 2016-08-31T14:36:18Z
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> "cordova platform add blackberry" fails on 2.7.1-rc.1
> -
>
> Key: CB-3232
> URL: https://issues.apache.org/jira/browse/CB-3232
> Project: Apache Cordova
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: BlackBerry, CLI
>Affects Versions: 2.7.0
>Reporter: Michael Brooks
>Assignee: Michael Brooks
> Fix For: 2.7.0
>
>
> The following error is thrown when running {{$ cordova platform add
> blackberry}}:
> {code}
> [Error: An error occured during creation of blackberry sub-project. Creating
> BlackBerry project...
> Updating config.xml ...
> sed:
> /Users/mwbrooks/Dropbox/Development/sandbox/myapp/platforms/blackberry/www/config.xml:
> No such file or directory
> Cleaning up ...
> Remember to update the project.properties file inside your application
> directory!
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455346#comment-15455346
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/80
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-geolocation
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-geolocation/pull/80.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #80
commit 096c186770e4b8176b3ee35ab17b4709d92eb304
Author: Vladimir Kotikov
Date: 2016-08-31T13:49:02Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets relea
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455336#comment-15455336
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-splashscreen/pull/113
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-splashscreen
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-splashscreen/pull/113.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #113
commit 67289f94353c7c8dbb2549a1f3566119d6548997
Author: Vladimir Kotikov
Date: 2016-08-31T14:41:02Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455347#comment-15455347
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-file/pull/194
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-file CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-file/pull/194.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #194
commit b85a483ca95c5038ee89fa237a9e986a7f6402a2
Author: Vladimir Kotikov
Date: 2016-08-31T13:45:32Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without adding
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455343#comment-15455343
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/184
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-inappbrowser
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-inappbrowser/pull/184.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #184
commit 733f087f5037003c09414234b3cb1126dd14f940
Author: Vladimir Kotikov
Date: 2016-08-31T14:17:31Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455353#comment-15455353
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-device/pull/55
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-device
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-device/pull/55.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #55
commit 24795aec50545d47dc28919ef07df31338c1d891
Author: Vladimir Kotikov
Date: 2016-08-31T13:29:57Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without add
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455355#comment-15455355
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-device-orientation/pull/29
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/vladimir-kotikov/cordova-plugin-device-orientation CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-device-orientation/pull/29.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #29
commit 7d72134339066c642dc39373a4a9e925c665fc60
Author: Vladimir Kotikov
Date: 2016-08-31T13:42:25Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455350#comment-15455350
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/157
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-file-transfer
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-file-transfer/pull/157.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #157
commit 62eef099971ee13d3644e9061deb8fcd30187877
Author: Vladimir Kotikov
Date: 2016-08-31T13:47:40Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} g
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455345#comment-15455345
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-globalization/pull/50
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-globalization
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-globalization/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
commit 9c1277d4f612af6c060ae498b7bf2da7be38fc52
Author: Vladimir Kotikov
Date: 2016-08-31T13:52:06Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455342#comment-15455342
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-media/pull/115
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-media CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-media/pull/115.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #115
commit 9ff23a24c14e4b558bb72660690c3efae42ca092
Author: Vladimir Kotikov
Date: 2016-08-31T14:33:54Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released without addi
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455328#comment-15455328
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-vibration/pull/49
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-vibration
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-vibration/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
commit fda15b6584263d349686dc3e925db9281697e379
Author: Vladimir Kotikov
Date: 2016-08-31T14:44:58Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released wi
[jira] [Commented] (CB-11795) Introduce cordovaDependencies to all core plugins
[
https://issues.apache.org/jira/browse/CB-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455326#comment-15455326
]
ASF GitHub Bot commented on CB-11795:
-
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-plugin-whitelist/pull/22
CB-11795 Add 'protective' entry to cordovaDependencies
### Checklist
- [ ] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and
submitted to secret...@apache.org.
- [ ] [Reported an issue](http://cordova.apache.org/contribute/issues.html)
in the JIRA database
- [ ] Commit message follows the format: "CB-3232: (android) Fix bug with
resolving file paths", where CB- is the JIRA ID & "android" is the platform
affected.
- [ ] Added automated test coverage as appropriate for this change.
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladimir-kotikov/cordova-plugin-whitelist
CB-11795
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-whitelist/pull/22.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22
commit 19f0778b731ff67b0dd1aa65f59dcf98fa833b5a
Author: Vladimir Kotikov
Date: 2016-08-31T14:47:34Z
CB-11795 Add 'protective' entry to cordovaDependencies
The entry is required to protect end-users from fetching edge versions of
the plugin by incompatible version of cordova. This also assumes that we will
not introduce any regressions in compatibility w/ cordova in minor and patch
releases. On every major release we will need to add similar entry with _next_
major version.
> Introduce cordovaDependencies to all core plugins
> -
>
> Key: CB-11795
> URL: https://issues.apache.org/jira/browse/CB-11795
> Project: Apache Cordova
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AllPlugins
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> We've been researching ways to prevent cordova workflow breakages, caused by
> installing edge versions of the plugins, which possibly could be incompatible
> with cordova version, used by user. This is IMO a very nasty sort of
> problems, because it might cause unpredictable build- and runtime failures of
> cordova setup which has been working perfectly previously.
> A typical example of this scenario is when some plugin introduces a change
> incompatible w/ some particular cordova version and doesn't update
> {{cordovaDependencies}} property in its' package.json correspondingly.
> To prevent such breakages and avoid negative user experience I propose to
> start using {{cordovaDependencies}} in core plugins in a following way:
> # For every plugin we maintain, we add `cordovaDependencies` to its'
> package.json w/ the following entry
> {noformat}
> CURRENT_PLUGIN_VERSION: { cordova: >= LATEST_SUPPORTED_CORDOVA_VERSION }
> {noformat}
> We will try to determine the {{LATEST_SUPPORTED_CORDOVA_VERSION}} based on
> release
> notes and most significant changes in plugins, but probably we can safely use
> 6.1.0 here because new version choosing logic for {{plugin add}} was
> introduced in this version and older versions of cordova will not use
> {{cordovaDependencies}} anyway.
> Also for some plugins adding such entry doesn't make sense because they will
> work with any version of cordova, so for these plugins this step could be
> omitted.
> # For every plugin we add additional 'protective' entry
> {noformat}
> NEXT_MAJOR_PLUGIN_VERSION: { cordova: >= 100 }
> {noformat}
> There are 2 purposes for this:
> - if there is a major plugin update that potentially would broke
> compatibility
> with some cordova versions, this will protect users against installing this
> major update, unless plugin maintainers update `cordovaDependencies` by adding
> corresponding entry for this plugin version.
> In other words, if we've introduced a breaking change and forgot to
> update {{cordovaDependencies}} correspondingly to reflect that the change
> requires a specific cordova version, user will not get this plugin update.
> - By some reason without such 'protective' entry in case if
> {{NEXT_MAJOR_PLUGIN_VERSION}} gets released wi
[jira] [Commented] (CB-11661) Camera plugin crashes on iOS 10
[ https://issues.apache.org/jira/browse/CB-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455323#comment-15455323 ] ASF subversion and git services commented on CB-11661: -- Commit 9fe94479e257c68e56a62cbd948382c12d947abf in cordova-plugin-camera's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=9fe9447 ] CB-11661: (ios) Add mandatory iOS 10 privacy description This commit adds corresponding change to README template so changes from a3af38a won't be lost > Camera plugin crashes on iOS 10 > --- > > Key: CB-11661 > URL: https://issues.apache.org/jira/browse/CB-11661 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Plugin Camera >Affects Versions: 3.5.0 > Environment: iOS 10 >Reporter: jcesarmobile >Assignee: jcesarmobile > > We need to add a privacy description to the plist. Since iOS 6 Apple provided > a way to show the user why a certain permission is required. In iOS 10 this > becomes mandatory, so any app not specifying the key will crash at runtime > when a permissions is requested. > This plugin requests the Camera permission, so at the very least we need to > add NSCameraUsageDescription and NSPhotoLibraryUsageDescription to the > `plist`. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9762) App icon and Launch image for iPad Pro
[ https://issues.apache.org/jira/browse/CB-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455280#comment-15455280 ] ASF GitHub Bot commented on CB-9762: GitHub user kerrishotts opened a pull request: https://github.com/apache/cordova-ios/pull/250 CB-9762 (iOS) Add launch storyboard support - [X] Signed ICLA - [X] Jira Issue: [CB-9762](https://issues.apache.org/jira/browse/CB-9762) - [X] Tests: - [X] Automated (npm test; all passing) Note: no automated tests for this functionality, though - [X] Manual (with and without launch storyboard images): - iPhone 6s (iOS 10b8) - iPad Pro (iOS 10b8) Note: The splashscreen plugin will require updating to use the new images; but I think that should be a separate (but related) issue. I don't think it will be difficult to add though (crossing my fingers)! Note: Documentation will need to be updated to reflect the changes in this PR Note: No default splash images are provided; they would be overwritten anyway upon adding the platform. I've added the images I used below:      You can merge this pull request into a Git repository by running: $ git pull https://github.com/kerrishotts/cordova-ios CB-9762 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/250.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #250 commit 12eb374e93987a260dce57b5be1acbe1279a61e1 Author: Kerri Shotts Date: 2016-08-24T22:49:20Z CB-9762 Add launch storyboard support NB: No default splash images are provided; they would be overwritten anyway upon adding the platform. > App icon and Launch image for iPad Pro > -- > > Key: CB-9762 > URL: https://issues.apache.org/jira/browse/CB-9762 > Project: Apache Cordova > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Affects Versions: 4.0.0 >Reporter: Manuel Martiarena >Assignee: Kerri Shotts > Labels: cordova-ios-4.1.1 > Attachments: Default-Landscape@2x~ipad-pro.png, > Default-Portrait@2x~ipad-pro.png > > > Provide app icon image and launch image for iPad Pro > iPad Pro (@2x) App icon required 167x167 > iPad Pro (@2x) Launch image required 2048 x 2732 (portrait) > 2732 x 2048 (landscape) > https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/IconMatrix.html -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11797) Media.getDuration() sometimes doesn't get the right duration on iOs
Guirec Sénéchal created CB-11797: Summary: Media.getDuration() sometimes doesn't get the right duration on iOs Key: CB-11797 URL: https://issues.apache.org/jira/browse/CB-11797 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: iOS, Plugin Media Environment: iOS 9.3.5 , Ionic, Cordova, cordova plugin media, cordova file plugin Reporter: Guirec Sénéchal Hi, I have an audioguide app, where i store audio and images directly on the phone. I store and then get the files with the cordova file plugin, and load it with cordova plugin media. On some tours, the duration gets multiplied by about 1,835 (i'm talking about the value i get directly from the media.getDuration() function), and on the other, the duration is just right. The issue only happens on iOS, it works perfectly fine on Android. I have no idea how you could recreate the bug. Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11796) cordova-plugin-media-capture gives wrong video orientation
Alex Rumba created CB-11796: --- Summary: cordova-plugin-media-capture gives wrong video orientation Key: CB-11796 URL: https://issues.apache.org/jira/browse/CB-11796 Project: Apache Cordova Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Android, Plugin Media Capture Affects Versions: 1.3.0, 6.3.1 Reporter: Alex Rumba My cordova version is 6.3.1 and cordova-plugin-media-capture version is 1.3.0. When i capture the video in potrait mode, the video file is played by HTML5 player 180 degree flipped. I am using cordova in ionic version 1.7.12 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11097) Clicking hyperlink in an iframe opens a system browser instead of navigating to it
[ https://issues.apache.org/jira/browse/CB-11097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454832#comment-15454832 ] Daniel Åberg commented on CB-11097: --- As there are still people watching this issue, just wanted to say we have been running Cordova 6.3.1 / IOS 4.2.0 for about a week now and do not have this problem anymore. So, totally fixed, and thank you to the Cordova team. > Clicking hyperlink in an iframe opens a system browser instead of navigating > to it > -- > > Key: CB-11097 > URL: https://issues.apache.org/jira/browse/CB-11097 > Project: Apache Cordova > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS, Plugin Whitelist >Affects Versions: 6.0.0, 6.1.1 > Environment: Cordova 6.1.1, iOS platform 4.1.1, developing in Visual > Studio 2015 with remote build server. Affects Cordova 6.0.0/iOS 4.0.0 and > later. Same behaviour on simulator and physical phone. >Reporter: Daniel Åberg >Assignee: jcesarmobile > Labels: ios, triaged > > From Cordova 6.0.0/iOS platform 4.0.0 and newer there is a change in behavior > or bug that stops navigating an anchor tag/hyperlink to an external site from > working. > If you have an iframe with a page with an anchor tag in which an href that > points to for an external domain it will now open it in the system browser > instead of loading it in the iframe. > It seems to have something to do how it handles if it’s going to navigate or > open in a new browser. > If you have the this in your configuration file you get this behavior: > > > http://*/*"; /> > https://*/*"; /> > If the allow-intent tags are removed, the iframe will load the page in the > href, so it seems like it first checks the intents and if its allowed it is > then opened in a new system browser regardless of other configuration. > This is a change in behavior, Cordova 5.4.1/iOS 3.9.2 navigated unless you > used InAppBrowser window.open() with target _system to open in the system > browser. > I have tried this with and without having Whitelist and InAppBrowser plugins > installed, I also tried the Cordova WKWebView Engine and got the same > behavior so I think it must be something in the iOS platform. > This issue might be related to the issue reported in CB-10709 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11343) Handle Java 9 after JEP 223
[
https://issues.apache.org/jira/browse/CB-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454783#comment-15454783
]
ASF GitHub Bot commented on CB-11343:
-
Github user ankon commented on the issue:
https://github.com/apache/cordova-android/pull/308
> So, how do we test this one? Is this a Mac OS X or Linux issue?
It's a "whereever you are able to run Java 9 (EA)"-issue.
> Handle Java 9 after JEP 223
> ---
>
> Key: CB-11343
> URL: https://issues.apache.org/jira/browse/CB-11343
> Project: Apache Cordova
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Android
>Affects Versions: 5.1.1
>Reporter: Andreas Kohn
>
> `cordova requirements android` fails on a system with Java 9(-ea) installed
> and accessible via PATH/JAVA_HOME:
> {code}
> $ cordova requirements android
> Requirements check results for android:
> Java JDK: not installed
> Cannot read property '1' of null
> Android SDK: installed
> Android target: installed
> android-17,android-18,android-19,android-21,android-22,android-23,android-N
> Gradle: installed
> Error: Some of requirements check failed
> $ echo $PATH
> /usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/andreas/.local/bin:/home/andreas/bin:/usr/java/jdk-9/bin:/home/andreas/modules/apache-maven/bin:/home/andreas/modules/apache-ant/bin:/home/andreas/modules/mongodb/bin:/home/andreas/modules/node/bin:/home/andreas/modules/android-sdk-linux/tools:/home/andreas/modules/android-sdk-linux/platform-tools
> $ which javac
> /usr/java/jdk-9/bin/javac
> $ echo $JAVA_HOME
> /usr/java/jdk-9
> $ javac -version
> javac 9-ea
> $ java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+120)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+120, mixed mode)
> {code}
> The exception is caused by the regular expression magic in check_reqs.js,
> `check_java` function:
> {code}
> var match = /javac ((?:\d+\.)+(?:\d+))/i.exec(output)[1];
> {code}
> (5.2.0-dev is slightly different, but has the same issue).
> I think the easiest fix here is to change the expression to this:
> {code}
> var match = /javac ((?:\d+\.)*(?:\d+))/i.exec(output)[1];
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10140) Use application id instead of package name when running
[ https://issues.apache.org/jira/browse/CB-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454695#comment-15454695 ] ASF GitHub Bot commented on CB-10140: - Github user CookieCookson commented on the issue: https://github.com/apache/cordova-android/pull/244 @infil00p I haven't had the time available to work any more on this, and have got around the issue by other means! I would say close it for now. > Use application id instead of package name when running > --- > > Key: CB-10140 > URL: https://issues.apache.org/jira/browse/CB-10140 > Project: Apache Cordova > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Android, CLI >Reporter: Christian Cook >Priority: Minor > > I've been working on a new plugin for Cordova which will allow you to easily > deploy different build types in a system lifecycle e.g. alpha, beta and > store. This will allow multiple instances of the same app on your device in > different states. Currently I've hit a bit of an interesting bug/issue when > using this in conjunction with the run command. When the plugin operates it > dynamically changes the application id depending on the state so com.test.app > becomes com.test.app.alpha and so son. Because of this, when running the app > from the CLI it then starts using the incorrect ID (it uses the packageName > from the Android Manifest and tries to run nothing or the wrong instance). > EDIT: See the PR for a suggested fix, and if you wish to try and replicate > this issue the plugin is now available here: > https://github.com/CookieCookson/cordova-plugin-lifecycle -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10140) Use application id instead of package name when running
[ https://issues.apache.org/jira/browse/CB-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454696#comment-15454696 ] ASF GitHub Bot commented on CB-10140: - Github user CookieCookson closed the pull request at: https://github.com/apache/cordova-android/pull/244 > Use application id instead of package name when running > --- > > Key: CB-10140 > URL: https://issues.apache.org/jira/browse/CB-10140 > Project: Apache Cordova > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Android, CLI >Reporter: Christian Cook >Priority: Minor > > I've been working on a new plugin for Cordova which will allow you to easily > deploy different build types in a system lifecycle e.g. alpha, beta and > store. This will allow multiple instances of the same app on your device in > different states. Currently I've hit a bit of an interesting bug/issue when > using this in conjunction with the run command. When the plugin operates it > dynamically changes the application id depending on the state so com.test.app > becomes com.test.app.alpha and so son. Because of this, when running the app > from the CLI it then starts using the incorrect ID (it uses the packageName > from the Android Manifest and tries to run nothing or the wrong instance). > EDIT: See the PR for a suggested fix, and if you wish to try and replicate > this issue the plugin is now available here: > https://github.com/CookieCookson/cordova-plugin-lifecycle -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
