Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of john.wargo@sap.com designates
 155.56.66.97 as permitted sender)
From: "Wargo, John" <john.wargo@sap.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Subject: Installing local plugin dependencies
Thread-Topic: Installing local plugin dependencies
Thread-Index: Ac92A0ejan5Ex+8UTfagFAPTHOmIIQ==
Date: Thu, 22 May 2014 21:17:50 +0000
Message-ID: 
 <5900F9BCB827854FB01CA94BA718810D40C8F81B@USPHLEMB11A.global.corp.sap>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_5900F9BCB827854FB01CA94BA718810D40C8F81BUSPHLEMB11Aglob_"
MIME-Version: 1.0

--_000_5900F9BCB827854FB01CA94BA718810D40C8F81BUSPHLEMB11Aglob_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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 lo=
cal dependencies, it fails because it simply can't resolve where those loca=
l plugins are. We know we can use the plugin_search_path on the command lin=
e, 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 plug=
ins more easily? I know where they all are, because they're all installed i=
n the same place (in separate folders of course).

--_000_5900F9BCB827854FB01CA94BA718810D40C8F81BUSPHLEMB11Aglob_--