Github user marti1125 commented on the pull request:
https://github.com/apache/cordova-firefoxos/pull/18#issuecomment-50462836
ok @zalun
---
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 f
GitHub user marti1125 opened a pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/20
[CB-6422] Use cordova/exec/proxy instead of platform dupes
https://issues.apache.org/jira/browse/CB-6422
[CB-6422] Use cordova/exec/proxy instead of platform dupes
You can m
GitHub user marti1125 opened a pull request:
https://github.com/apache/cordova-plugin-inappbrowser/pull/54
[CB-6422] Use cordova/exec/proxy instead of platform dupes
https://issues.apache.org/jira/browse/CB-6422
[CB-6422] Use cordova/exec/proxy instead of platform dupes
You can
GitHub user marti1125 opened a pull request:
https://github.com/apache/cordova-plugin-network-information/pull/15
[CB-6422] Use cordova/exec/proxy instead of platform dupes
https://issues.apache.org/jira/browse/CB-6422
[CB-6422] Use cordova/exec/proxy instead of platform dupes
GitHub user marti1125 opened a pull request:
https://github.com/apache/cordova-plugin-vibration/pull/18
[CB-6422] Use cordova/exec/proxy instead of platform dupes
https://issues.apache.org/jira/browse/CB-6422
[CB-6422] Use cordova/exec/proxy instead of platform dupes
You can mer
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-blackberry/pull/169
---
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 fea
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-firefoxos/pull/18
---
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 featu
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-file/pull/66
---
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 fea
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-splashscreen/pull/22
CB-7196 port splashscreen tests to framework
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stacic/cordova-plugin-splashscre
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-statusbar/pull/12
CB-7195 ported statusbar tests to framework
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stacic/cordova-plugin-statusbar CB-7
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-plugin-network-information/pull/13#issuecomment-50518791
Personally, I don't want commit messages to have spelling errors in them.
---
If your project is set up for it, you can reply to this email and
GitHub user surajpindoria opened a pull request:
https://github.com/apache/cordova-lib/pull/66
CB-7190: Add browserify support in cordova-lib/cordova-cli
https://issues.apache.org/jira/browse/CB-7190
You can merge this pull request into a Git repository by running:
$ git pull h
GitHub user surajpindoria opened a pull request:
https://github.com/apache/cordova-cli/pull/185
Added browserify flag to cli options
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/surajpindoria/cordova-cli CB-7001
Alternatively
Hi everyone,
I have been working with Anis and Steve to add browserify support in
cordova-lib and cordova-cli. They way this is being done is through a flag in
the CLI which then calls prepare-browserify versus the standard prepare, an
example:
"cordova plugin --browserify add org.apache.cordo
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15544876
--- Diff: cordova-lib/src/plugman/plugman.js ---
@@ -70,6 +70,7 @@ addProperty(plugman, 'install', './install', true);
addProperty(plugman, 'uni
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-cli/pull/186
CB-7220 Split cordova help into per feature help files
This splits the documentation for the various commands into individual
files.
It also exposes the bash help (although it doesn't m
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15545141
--- Diff: cordova-lib/src/plugman/uninstall.js ---
@@ -316,6 +316,10 @@ function handleUninstall(actions, platform, plugin_id,
plugin_et, project_di
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15545303
--- Diff: cordova-lib/src/plugman/install.js ---
@@ -571,7 +571,11 @@ function handleInstall(actions, pluginInfo, platform,
project_dir, plugins_dir
Hi.
https://issues.apache.org/jira/browse/CB-6024
Broke a number of people. While there was a pull request and a bug, there
wasn't a major version bump.
People using npm w/ grunt-cordovacli in a continuous integration setting
w/ reasonable package.json settings went from having a working build
Github user kamrik commented on the pull request:
https://github.com/apache/cordova-cli/pull/186#issuecomment-50524957
Looks good.
---
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
cordova prepare --browserify works too
https://issues.apache.org/jira/browse/CB-7001
https://issues.apache.org/jira/browse/CB-7190
On Tue, Jul 29, 2014 at 12:02 PM, Suraj Pindoria <
suraj.pindo...@yahoo.com.invalid> wrote:
> Hi everyone,
>
> I have been working with Anis and Steve to add browse
How do you all feel about a plugins release?
I can aim to start a vote thread tomorrow or Thursday if people feel good
about it.
-Steve
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-geolocation/pull/20
---
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 asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-inappbrowser/pull/54
---
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 asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-network-information/pull/15
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-vibration/pull/18
---
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 th
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-cli/pull/186
---
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 is
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-camera/pull/39
---
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 f
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-device-motion/pull/15
---
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 i
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-contacts/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 the
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-device-orientation/pull/12
---
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,
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-device/pull/18
---
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 f
Started creating issues to keep track of all of these things.
Master issue can be seen at https://issues.apache.org/jira/browse/CB-7221
Setting CLI to version 4.0.0 sounds good to me. We can mention in the
release blog post how platforms are on their own schedule now.
Option 3 for docs
- Docs ge
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-dialogs/pull/24
---
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 stevengill commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15553301
--- Diff: cordova-lib/src/plugman/uninstall.js ---
@@ -316,6 +316,10 @@ function handleUninstall(actions, platform, plugin_id,
plugin_et, project_dir,
Current cli is cadver-semver and if even if we had bumped the semver MAJOR
it would not have mattered. If you were using semantic version matching in
your package.json for cli dependancy, the current scheme does not match the
way you expect. Josh your suggestion is that we should have used our
ca
Just to confirm: Can I run "cordova prepare --browserify" is any existing
workspace, or would I have needed to add all plugins / platforms with that
flag as well?
-Michal
On Tue, Jul 29, 2014 at 3:27 PM, Steven Gill wrote:
> cordova prepare --browserify works too
>
> https://issues.apache.org/
Github user purplecabbage commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15553576
--- Diff: cordova-lib/src/plugman/uninstall.js ---
@@ -316,6 +316,10 @@ function handleUninstall(actions, platform, plugin_id,
plugin_et, project_di
Github user stevengill commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15553653
--- Diff: cordova-lib/src/plugman/plugman.js ---
@@ -70,6 +70,7 @@ addProperty(plugman, 'install', './install', true);
addProperty(plugman, 'uninst
Github user stevengill commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/66#discussion_r15553915
--- Diff: cordova-lib/src/plugman/uninstall.js ---
@@ -316,6 +316,10 @@ function handleUninstall(actions, platform, plugin_id,
plugin_et, project_dir,
Right now it only works when you add the plugins with the flag.
Current working use case:
-Create a project
-Add platform
-Add plugins with browserify flag
Adding a platform after does not use the proper browserify-prepare. Obviously
an issue.
We just realized an issue we need to solve first.
Definitely no developer tests all possible combinations, that’s not feasible :/
More likely these manual tests (at least how I’ve used them) is to verify a
Camera bug, then verify the fix to the bug worked.
It’s not ideal of course since the fix could break some other functionality,
but I don’t h
Decided to add a few more issues and organize around a master issue.
https://issues.apache.org/jira/browse/CB-7190
If you guys think of other use cases, let us know!
On Tue, Jul 29, 2014 at 2:47 PM, Suraj Pindoria <
suraj.pindo...@yahoo.com.invalid> wrote:
> Right now it only works when you ad
Carlos, Jesse and Joe,
Thank you guys, loads of helpful info! I will go with the renaming as
suggested and it seems like even from the user side it won't be as painful
as I anticipated, so thanks for the additional info.
Losing control over the releases and contributions is indeed a bit of a
pai
Michal wrote:
> Current cli is cadver-semver and if even if we had bumped the semver MAJOR it
> would not have mattered.
> If you were using semantic version matching in
your package.json for cli dependancy,
> the current scheme does not match the way you expect.
> Josh your suggestion is that we
if you know of assumptions on cordova cli like passing extra arguments down
to the platform scripts (i.e. emulate), this is something that can be added
to the unit tests for cordova-lib, this way it's part of the CI tests with
"npm test"
you can mockup the expected call down to the platforms script
Sounds like a setting that would go well in .cordova/config.json, I think.
-Michal
On Tue, Jul 29, 2014 at 6:10 PM, Steven Gill wrote:
> Decided to add a few more issues and organize around a master issue.
>
> https://issues.apache.org/jira/browse/CB-7190
>
> If you guys think of other use cas
Throwing out another option: can we just patch cli now to pass arguments on
like it used to, even with the new nopt? Failing that, I don't mind
reverting the config changes and releasing tools again, assuming we're
going to get 4.0 out soon anyway.
Josh: RE CI -- I look forward to your patch for
Yep Michal I agree to update cli to pass down extra parameters to platform
scripts like it used. this allow for greater flexibility in platform
scripts and no hardcoded platform concerns in cli. No need to remove nopt
if the this can be achieved.
On Tue, Jul 29, 2014 at 10:45 PM, Michal Mocny w
49 matches
Mail list logo
