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 mmocny@google.com designates
 209.85.212.43 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CAHcDwFxZ=tRyfacReHaRjp4QVcrZdZZtw00Nn1sfEXLEyHFH2g@mail.gmail.com>
References: 
 <CE8995AB5D178F44A2154F5C9A97CAF40258E6F45BE8@HE111541.emea1.cds.t-internal.com>
 <CAK_TSXJp4RhbqtYTUVZEBNyv9ZebfTPZEHSzhhuGYtw5XBp1vg@mail.gmail.com>
 <CAHcDwFyn2Nd=L7=8Gc3niy3K=WRww7X3jZfJ-cjKXEWoJbggdA@mail.gmail.com>
 <CAEeF2TffFDcZ7Smr8LZyfX9RL-HVVSD6bg6Lo7FxxBOrQ5zeMg@mail.gmail.com>
 <CAHcDwFxZ=tRyfacReHaRjp4QVcrZdZZtw00Nn1sfEXLEyHFH2g@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Mon, 21 Oct 2013 17:15:23 -0400
Message-ID: 
 <CAEeF2TcyYPrNVFX-i1VMdwY6HQ7YwrkXk9O8C2_q1SZsxQGEUw@mail.gmail.com>
Subject: Re: www/config.xml plugin dependencies
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b339df97a0ecd04e946c923

--047d7b339df97a0ecd04e946c923
Content-Type: text/plain; charset=ISO-8859-1

Maybe we do just go the npm style route.

cordova plugin add (without ID) -> reads deps from config and installs them.
cordova plugin add --save-deps ID -> adds plugin and adds to config
cordova plugin add --save-deps (without ID)-> takes installed plugins and
adds to deps

something like that?


On Mon, Oct 21, 2013 at 4:24 PM, Axel Nennker <ignisvulpis@gmail.com> wrote:

> A MUST would be strong I think. Although the two ways don't mix well.
> Using dependency and plugin-add simultaneously is probably wrong.
> So plugin-add could look for www/config.xml dependency elements and suggest
> to continue to use them if one is found. If none is found then it adds the
> plugin.
>
> Updating plugins during create/prepare would be a good start.
> Plugins could be removed when the subdirs of the plugins directory and the
> dependency elements indicate it.
>
> Axel
>  Am 21.10.2013 20:35 schrieb "Michal Mocny" <mmocny@chromium.org>:
>
> > We've discussed adding <dependancy> to app's config.xml, but its
> > interesting that you intend to have that work during build/prepare step.
> >  Previously I think this was discussed in terms of "cordova create" only,
> > which wouldn't satisfy your use case.  I think your use case is quite
> > valid, but now im concerned about how to support removed <dependancy>
> over
> > time, or manually installed plugins that arent in <dependancy> list...
> >
> > Maybe every plugin installed/removed *must* be reflected in the app's
> > config.xml?
> >
> > -Michal
> >
> >
> > On Mon, Oct 21, 2013 at 1:42 PM, Axel Nennker <ignisvulpis@gmail.com>
> > wrote:
> >
> > > Yes. Currently we are adding plugin be hand.
> > > The problem is that we have a distributes developer team. So when the
> UI
> > > developers change something in www to require a plugin and merge that
> > with
> > > master; then when the other developers pull master again the plugin is
> > > missing and the Application hangs.
> > > This has led to some frustration and wasted time.
> > >
> > > I think it would really help if www - developers could express a
> > dependency
> > > on plugins so that the next
> > >     phonegap local android build
> > > updates to the now missing plugins...
> > >
> > > cheers
> > > Axel
> > >
> > >
> > > 2013/10/21 Ian Clelland <iclelland@chromium.org>
> > >
> > > > I don't think that we have "app dependencies" in Cordova (yet). If
> your
> > > app
> > > > depends on a plugin, then you should install that plugin.
> > > >
> > > > Either "cordova plugin add org.apache.cordova.globalization" or
> > "plugman
> > > > install org.apache.cordova.globalization" (not sure about the command
> > > line
> > > > params there) should add the plugin and modify your config.xml file
> > > > appropriately.
> > > >
> > > > If you're concerned about automation / distribution, and want a
> simple
> > > way
> > > > to declare all of your app's dependent plugins, rather than just
> > > > documenting them, then you can use the technique that mobile-spec
> > > uses[1]:
> > > > Create a "dependency-only plugin" which just lists all of the plugins
> > on
> > > > which your app depends, and as part of your create step, install that
> > > > single plugin. Cordova will then recursively install all of the
> > > > dependencies listed in it.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://github.com/apache/cordova-mobile-spec/tree/master/dependencies-plugin
> > > >
> > > >
> > > > On Mon, Oct 21, 2013 at 10:44 AM, <Axel.Nennker@telekom.de> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > the docs in
> > > > >
> > > >
> > >
> >
> https://cordova.apache.org/docs/en/3.1.0/config_ref_index.md.html#The%20config.xml%20Filesaythatthefeatureelement is only for the platform specific config.xml
> > > > > s, right?
> > > > >
> > > > > Is there a way to specify that my phonegap app needs a plugin on
> all
> > > > > platforms e.g. Globalization?
> > > > >
> > > > > Making up this "example":
> > > > > https://cordova.apache.org/docs/en/3.0.0/plugin_ref_spec.md.html
> > > > > <gap:dependency id="com.plugin.id" url="
> > > > > https://github.com/myuser/someplugin" commit="428931ada3891801"
> > > > > subdir="some/path/here" />
> > > > >
> > > > > We are building an app that uses Globalization in javascript; so
> > there
> > > is
> > > > > no platform dependency
> > > > > How do I specifiy in www/config.xml that Globalization is needed
> as a
> > > > > plugin?
> > > > >
> > > > > Cheers
> > > > > Axel
> > > > >
> > > >
> > >
> >
>

--047d7b339df97a0ecd04e946c923--