cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Installing local plugin dependencies
Date Fri, 23 May 2014 14:40:26 GMT
If you're not interested in publishing to the registry, I think using
<dependency> that contains relative paths works fine. It's a bit quirky
though.


On Thu, May 22, 2014 at 5:44 PM, Michal Mocny <mmocny@chromium.org> wrote:

> Chrome apps for mobile initially tried using local dependencies to solve
> the project-create-plugin-add while offline case.  In the end, it didn't
> work for us, and isn't clear that it could ever work.  E.g. if you specify
> local deps in your plugins, you cannot publish those plugin to registry.
>  You'd need two different dependency syntaxes depending on how a plugin is
> fetched/installed, and thats just confusing.
>
> Search path really is your way to go, but you don't need to use it
> explicitly from the command line.. you can set default "plugin_search_path"
> array in your .cordova/config.json.
>
>
> On Thu, May 22, 2014 at 5:17 PM, Wargo, John <john.wargo@sap.com> wrote:
>
> > We distribute our Kapsel SDK (our set of Cordova plugins) as an
> > installable package. We're running into a problem when we install a
> plugin
> > that has local dependencies, it fails because it simply can't resolve
> where
> > those local plugins are. We know we can use the plugin_search_path on the
> > command line, but this solution feels clunky and think there has to be a
> > better way.
> >
> > Is there a better way?
> >
> > Can't I configure the plugins some way so that they point to the local
> > plugins more easily? I know where they all are, because they're all
> > installed in the same place (in separate folders of course).
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message