Would have the benefit of enabling a plugin, and plugin-test existence
in a single repo. Consolidates a lot of tooling. Lets discuss more
herein
The main technical ask here is the ability to specify a plugin as { git
repo, commit hash, subdirectory } instead of just { git repo, commit hash }.
On Fri, Mar 22, 2013 at 2:05 PM, Brian LeRoux b...@brian.io wrote:
Would have the benefit of enabling a plugin, and plugin-test existence
in a
I'm into it.
On Fri, Mar 22, 2013 at 11:11 AM, Max Woghiren m...@chromium.org wrote:
The main technical ask here is the ability to specify a plugin as { git
repo, commit hash, subdirectory } instead of just { git repo, commit hash }.
On Fri, Mar 22, 2013 at 2:05 PM, Brian LeRoux b...@brian.io
This has all of my +1s. Especially if our testing story is a dependent
plugin, this is way more convenient than two repos.
Braden
On Fri, Mar 22, 2013 at 2:19 PM, Brian LeRoux b...@brian.io wrote:
I'm into it.
On Fri, Mar 22, 2013 at 11:11 AM, Max Woghiren m...@chromium.org wrote:
The
Huge +1.
Questions:
1. Could we allow installing multiple plugins/subdirectories from within
the same repo in one step. Support wildcards? (i.e. cordova plugin add
--repo=git --version=hash --name=*)
2. Should we cache git repos so we dont need clone over and over for each
plugin and app.
(1) That seems useful (eg. install plugin_foo and plugin_foo_test in one
command). Maybe, by default, omitting the `--name` parameter could install
all plugins found in the specified repo/hash.
(2) I think there's theoretical value in this, but cloning is somewhat
cheap so it's probably not
