Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of kamrik@google.com designates
 209.85.219.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADVgkyNPkh4948tTNAE-eAqJm+JBb6eHYaTPut_RSOm4_WDsQA@mail.gmail.com>
References: 
 <85A3E123BABF314D9D3656D0B418125643E0E4D8@FMSMSX103.amr.corp.intel.com>
	<CAEeF2Td9-=cvVO9i8r-nBhsvEdiDDhK25t02W8Mbp4zA9qVxrw@mail.gmail.com>
	<ef5d3079cb1942e9b95122cab20ca838@BLUPR03MB065.namprd03.prod.outlook.com>
	<85A3E123BABF314D9D3656D0B418125643E0E886@FMSMSX103.amr.corp.intel.com>
	<8eff060366a445ad94162c2f1adfbdc7@BLUPR03MB065.namprd03.prod.outlook.com>
	<20140814081559.GA6390@gmail.com>
	<CAEeF2TdtnmZFoTMJ4dFhYM4rwKzu9pJ5BsKcuBsvgagX_P3GxA@mail.gmail.com>
	<85A3E123BABF314D9D3656D0B418125643E10D34@FMSMSX103.amr.corp.intel.com>
	<CAEeF2Tc1mQUr6aRiiJ3VLy3_+m15HX04qFSig69Fjwdm7PaDTg@mail.gmail.com>
	<a389cff113cd45e29253c1c1ede7fa8e@DM2PR03MB366.namprd03.prod.outlook.com>
	<CADVgkyNPkh4948tTNAE-eAqJm+JBb6eHYaTPut_RSOm4_WDsQA@mail.gmail.com>
Date: Mon, 18 Aug 2014 17:16:32 -0400
Message-ID: 
 <CA+GVa3ZC6a2Ejk25dYfWQqx404VYA4Nur2KDUyANyWVeCXTc2Q@mail.gmail.com>
Subject: Re: cordova plugin save
From: Mark Koudritsky <kamrik@google.com>
To: dev@cordova.apache.org
Cc: "Treggiari, Leo" <leo.treggiari@intel.com>
Content-Type: multipart/alternative; boundary=089e01161dc09461e90500ede2b3

--089e01161dc09461e90500ede2b3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In order to keep the plugins as project deps in package.json we need to
sort out some details of treating plugins as npm packages first:

1) Plugins don't currently have package.json files, and list their deps in
plugin.xml.
2) Are we ok with loosing the possibility of specifying platform specific
dependencies? (e.g. plugin A might depend on plugin B for iOS and on
nothing for Android)
3) Simply listing deps inside the newly created package.json in plugins
will create a possibly deep tree of plugin/node_modules/plugin folders with
possible duplicates. Npm's peer dependencies
<http://blog.nodejs.org/2013/02/07/peer-dependencies/> might be the right
solution, but I haven't looked at it yet.

=E2=80=8B
I agree that Cordova is a build system to a very large extent. But then it
makes more sense to treat it as a tool to be used by other build systems
rather than re-invent all the wheels on our own.

Recently I tried building a cordova project with Gulp without using the
CLI, it works great.
https://github.com/kamrik/CordovaGulpTemplate

Some time ago Carlos did a similar thing with Grunt:
https://www.npmjs.org/package/grunt-cordovacli

--089e01161dc09461e90500ede2b3--