Github user sviluppatoribk commented on the pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/85#issuecomment-104544749
Please can you tell me what error code you get instead of 401? Test 6 of
file-transfer-plugin call
GitHub user alsorokin opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/130
CB-8843 Fixed mobilespec tests to pass on Android
https://issues.apache.org/jira/browse/CB-8843
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-registry-web/pull/9
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-android/pull/176
CB-8954 Adds support for `requirements` command
Implemetation for https://issues.apache.org/jira/browse/CB-8954
You can merge this pull request into a Git repository by running:
afaik, it's still available, but probably we'd need to ping INFRA to make
it alive again (doesn't respond to pings atm)
On Thu, May 21, 2015 at 5:59 PM, Dmitry Blotsky dblot...@microsoft.com
wrote:
Hey folks,
Resurrecting an old thread here: is cordova-vm.apache.org still available
for us?
It's been a while since we discussed this, and I'd like to implement the
change. I'd like to get some consensus on whether we should go with accepting
patch changes only ('~1.2.3') or accepting minor version changes ('^1.2.3').
Should we go with patch changes only for now, and see how things
Github user TimBarham commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/292#discussion_r30933383
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,70 @@
+---
+license: Licensed to the Apache Software Foundation
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104784245
So, I discussed this a bit with Steve, and he brought up an interesting
point.
A stretch goal is to not have a plugin.xml file at all, and simply use
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104788948
Yeah, I like that better.
If we fail to find it in our typical id search, we then retry with the
addition of `cordova-plugin-`
Incidentally,
Hey Jesse,
Yes, we can definitely have Medic run with different configurations. We have a
full test matrix that we can set up. Currently the biggest problem is: there is
a “clone and build” step that takes about 5 minutes of the time of every build,
and running it for every configuration does
Github user TimBarham commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104762109
Hah, yeah, I think that'd definitely be doable. I won't include it as part
of this change, though.
---
If your project is set up for it, you can reply to this
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/292#discussion_r30932290
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,70 @@
+---
+license: Licensed to the Apache Software
Hi list,
Here are some points of interest regarding the CI:
- Builds now know what commits went into them
- Waiting on Infra to configure GitHub repos to send changes our way
so that they will *trigger* the builds (right now they're still periodic)
- Windows build
Github user TimBarham commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104787089
Hmmm... Interesting point. I like the convenience of a short name, but I
don't think it is worth the weirdness of adding a custom field to package.json
just for
I'm okay with accepting patch changes without upgrading the tooling for
now. If it works well and once we have more extensive testing in place, we
can swap to accepting minor changes.
-Steve
On Fri, May 22, 2015 at 2:21 PM, Tim Barham tim.bar...@microsoft.com
wrote:
It's been a while since we
Github user TimBarham commented on the pull request:
https://github.com/apache/cordova-docs/pull/292#issuecomment-104768868
You should also describe what happens if you add a platform (via `cordova
platform add`) that has an entry saved in `config.xml` (specifically that if
you add
Github user TimBarham commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/292#discussion_r30932058
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,70 @@
+---
+license: Licensed to the Apache Software Foundation
Github user muratsu commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104789786
:+1:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Hi all,
During the work on translation, I always in rush to produce it before
release, because of docs updated not very often. Maybe we could configure
Git to publish docs after commit, so on CrowdIn would be always the latest
docs?
Thanks
Github user TimBarham commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/292#discussion_r30929325
--- Diff: docs/en/edge/platform_plugin_versioning_ref/index.md ---
@@ -0,0 +1,70 @@
+---
+license: Licensed to the Apache Software Foundation
Thanks for the update Dmitry!
I have kept somewhat distant from the intricacies of our CI, so I have a
few questions.
Do you think we can get Medic running different build variations, like with
and without the --browserify flag?
Can we have Medic run tests for every pull request and report
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-ios/pull/142
CB-8954 Adds support for `requirements` command
Implemetation for https://issues.apache.org/jira/browse/CB-8954
You can merge this pull request into a Git repository by running:
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-windows/pull/83
CB-8954 Adds support for `requirements` command
Implementation for https://issues.apache.org/jira/browse/CB-8954
You can merge this pull request into a Git repository by running:
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-wp8/pull/82
CB-8954 Adds support for `requirements` command
Implementation for https://issues.apache.org/jira/browse/CB-8954
You can merge this pull request into a Git repository by running:
Github user Gillardo commented on the pull request:
https://github.com/apache/cordova-plugin-statusbar/pull/25#issuecomment-104608748
@nikhilkh i have emailed the agreement to secret...@apache.org this morning
for you.
---
If your project is set up for it, you can reply to this
I'm the only one working on this unfortunately -- the agile board is
here: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=76
On Fri, May 22, 2015 at 8:10 AM, Homer, Tony tony.ho...@intel.com wrote:
In March, Shazron mentioned a tentative April release[1]. Can we get an
In March, Shazron mentioned a tentative April release[1]. Can we get an
updated estimate?
Are there tasks that need help before it can move forward?
[1]
https://shazronatadobe.wordpress.com/2015/03/03/wkwebview-and-apache-cordov
a/
Thanks!
Tony
Github user Gillardo commented on the pull request:
https://github.com/apache/cordova-plugin-statusbar/pull/25#issuecomment-104697601
This message acknowledges receipt of your ICLA, which has been filed in the
Apache Software Foundation records.
If you have been invited as a
CORS does not apply for local content using file:///, hence, browser will allow
all XHRs when your origin is local. When you host content on remoteserver.com
CORS is applied. If you make an XHR to xhr.com, the browser will pre-flight a
request to xhr.com asking if xhr.com supports xhr access
Github user infil00p commented on the pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/36#issuecomment-104742963
Just as @jcesarmobile said, there are no modules needed, therefore this
should be closed. Because this is a copy of the repository, and not the
GitHub user omefire opened a pull request:
https://github.com/apache/cordova-docs/pull/292
CB-8900: Documentation for the platform save / restore feature
This PR's goal is to document the platform save / restore feature.
I'll soon send another one for the plugin side of things.
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-contacts/pull/60
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user omefire commented on the pull request:
https://github.com/apache/cordova-docs/pull/292#issuecomment-104746042
I'll soon send another one for the plugin side of things.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-contacts/pull/63
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
GitHub user TimBarham opened a pull request:
https://github.com/apache/cordova-lib/pull/225
CB-9065 Allow removing plugins by short name.
Adds logic to `plugin remove` to look up a plugin by short name if we
don't find it by id. This means, for example, that you can use the
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-geolocation/pull/36
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-lib/pull/225#issuecomment-104747950
Interesting, I like it.
How about removing by path/url?
Does it make sense having installed via `cordova plugin add ../myplugin/`
that I could
Thanks for the explanation. This change and workflow makes sense now.
Currently, createmobilespec.js is used by the Cordova CI:
http://ci.apache.org/builders/cordova-windows-phone8.1/builds/4/steps/creating-mobilespec-app/logs/stdio
The intent of the CI is to test the latest unreleased version
Does anyone have reason to delay this release? This is the first release with
Windows 10 support and has a breaking change that requires an accompanying
tools release. Hence, I propose we version it 4.0.0
Here are the next steps:
- Prepare blog for the release include details of
Github user recursion1122 commented on the pull request:
https://github.com/apache/cordova-plugin-contacts/pull/61#issuecomment-104730019
This seems to occur with at least moderate consistency on Samsung Galaxy S5
devices running Android 5.x. I tested it on two different devices and
40 matches
Mail list logo
