cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: Removal of <plugins> from config.xml
Date Thu, 16 May 2013 20:30:00 GMT
+1, and another point: make sure your native bits continue to load from
both <plugin/> and <feature/> until the deprecation window slams shut.

@purplecabbage
risingj.com


On Thu, May 16, 2013 at 12:56 PM, Benn Mapes <benn.mapes@gmail.com> wrote:

> +1 to leave in an empty <plugin/> until deprecation time is reached, it
> just makes sense.
>
>
> On Thu, May 16, 2013 at 12:51 PM, Gorkem Ercan <gorkem.ercan@gmail.com
> >wrote:
>
> > +1 for a deprecation period
> >
> > --
> > Gorkem
> >
> >
> > On Thu, May 16, 2013 at 3:45 PM, Filip Maj <fil@adobe.com> wrote:
> >
> > > We deprecated this recently. Can we leave an empty <plugins> element
in
> > > config.xml for each platform while the deprecation window is still
> open?
> > > This way tooling such as plugman can still add <plugin> elements while
> > the
> > > platforms still support it.
> > >
> > > Once we fully remove <plugin> support then IMO that is the right time
> to
> > > completely remove the <plugins> element from config.xml.
> > >
> > > Also makes life easier for services consuming cordova (*cough* PhoneGap
> > > Build *cough*). :)
> > >
> > > Lemme know what you guys think.
> > >
> > >
> >
>

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