Github user asfgit closed the pull request at:
https://github.com/apache/cordova-windows/pull/123
---
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 ghenry22 commented on the pull request:
https://github.com/apache/cordova-windows/pull/123#issuecomment-151123814
tested with the mod as in the comments, resolved the error for me
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ghenry22 commented on the pull request:
https://github.com/apache/cordova-windows/pull/123#issuecomment-151005434
Currently blocked preparing my first windows store submission by this one.
I use an external path to x64 node in visual studio 2015 so that it uses an
Github user SomaticIT commented on the pull request:
https://github.com/apache/cordova-windows/pull/123#issuecomment-150876679
@robpaveza @nikhilkh @rakatyal
Any news on this, it's a really painful error.
The error in tests is an issue in @robpaveza fix
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-windows/pull/123#issuecomment-149647416
@rakatyal Can you please take a look at this one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-windows/pull/123#issuecomment-146366478
@robpaveza Any update on this?
---
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
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-lib/pull/264
CB-9291 Fixes Appveyor build failure
This fixes Appveyor build failure, introduced by
https://github.com/apache/cordova-js/commit/eb620e2934e2d6706e71a2f8957343935d6dcf32
You can
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/264
---
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 feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/191
---
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 nikhilkh commented on the pull request:
https://github.com/apache/cordova-android/pull/191#issuecomment-118369603
LGTM
---
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
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-android/pull/191
CB-9286 Fixes build failure when ANDROID_HOME is not set.
This fixes [CB-9286](https://issues.apache.org/jira/browse/CB-9286) which
is a regression from 4bf705a.
You can merge
The CI always uses master cli and master plugman using this procedure:
git clone CLI
npm install (installs the 'wrong' plugman)
delete the node-modules/plugman directory
git clone plugman (into node-modules/plugman)
npm install (plugman)
When CLI refers to a plugman that does not exist, the
There is an interesting issue with detecting change though.
The failure is detected easily because a commit to CLI triggered a build.
The only reason I knew it was fixed was because a commit to JS caused a
rebuild on the Master branches (which worked).
Ideally, updating the plugman NPM module
David,
One thing you can can try is after you clone cordova-cli
edit cordova-cli package.json to point to a Git URL instead of npm for
plugman, this is before running npm install on cli
from this:
plugman: 0.14.x,
pick one: base on [1]
plugman: apache/cordova-plugman.git#0.14.x,
plugman:
I think you can also install plugman into node_modules *before* running
cli's npm install and it will not try to fetch from npm since there is
already a compatible version there.
-Michal
On Tue, Oct 29, 2013 at 8:15 AM, Carlos Santana csantan...@gmail.comwrote:
David,
One thing you can can
Our CI is failing with the message:
Error: No compatible version found: plugman@'=0.14.0- 0.15.0-'
npm ERR!
That is because I pushed plugman + cli to master but not to npm yet. That
will go away right when they get published to npm. After some more views on
the review of the blog post I will publish them.
On Monday, October 28, 2013, David Kemp wrote:
Our CI is failing with the message:
Error: No
If you are using both versions off master, why are you getting that error
message?
Seems it may happen if using master CLI and running npm install without
linking plugman first?
On Mon, Oct 28, 2013 at 9:52 PM, Steven Gill stevengil...@gmail.com wrote:
That is because I pushed plugman + cli
Just pulled latest cli/plugman to check that the version numbers deps,
and seems that they are. So im guessing its a tooling version mismatch on
the CI machine (using dev cli with released plugman).
-Michal
On Tue, Oct 29, 2013 at 12:57 AM, Michal Mocny mmo...@chromium.org wrote:
If you are
I am assuming the cli is doing npm install without linking. I changed the
plugman dependency to use 0.14.0 which wasn't live on npm at the time. I
pushed it to npm a little while ago. The tests should be be working now.
On Mon, Oct 28, 2013 at 9:57 PM, Michal Mocny mmo...@chromium.org wrote:
Hey David,
I just uploaded a patch that should hopefully things for ya. Let me know if
there are any more problems.
On 18 October 2013 18:51, Tim Kim timki...@gmail.com wrote:
Hrmmm. Shoot. Funny how a '.0' can paint you into a corner.
I'm not sure if there are any easy solutions to this
Looks like it fixed it!
On Oct 21, 2013 4:40 PM, Tim Kim timki...@gmail.com wrote:
Hey David,
I just uploaded a patch that should hopefully things for ya. Let me know if
there are any more problems.
On 18 October 2013 18:51, Tim Kim timki...@gmail.com wrote:
Hrmmm. Shoot. Funny how a
Woo!
On 21 October 2013 15:59, David Kemp drk...@google.com wrote:
Looks like it fixed it!
On Oct 21, 2013 4:40 PM, Tim Kim timki...@gmail.com wrote:
Hey David,
I just uploaded a patch that should hopefully things for ya. Let me know
if
there are any more problems.
On 18
Builds are failing due to an inability to add plugins.
This started about 8:2pm with three plugman commits by Tim Kim
error text:
Fetching plugin from ../cordova-mobile-spec/dependencies-plugin...
Starting installation of org.cordova.mobile-spec-dependencies for
ios[Error: Different version
Hey there David,
I just committed a fix for mobile spec. I believe the problem was that the
engine tag in cordova-mobile-spec/dependencies-plugin/plugin.xml needed to
have a patch portion to the version.
On 18 October 2013 17:48, David Kemp drk...@chromium.org wrote:
Builds are failing due to
Hi Tim,
That has indeed fixed the master branch, but the 3.1 release branch still
has the problem. I currently always build with the latest tool chain
(plugman) so a non backward-compatible change to plugman will be an issue.
That would require that the fix to mobilespec be back-patched to 3.1 as
Hrmmm. Shoot. Funny how a '.0' can paint you into a corner.
I'm not sure if there are any easy solutions to this one since the code
always pulls the latest. I think what I'll do is add some logic such that
the new version-compare in plugman can handle differing version strings.
Unfortunately it's
27 matches
Mail list logo
